-
-
Notifications
You must be signed in to change notification settings - Fork 641
EncryptionManager: un-deprecating EncryptionManager.getEncryptionKeys #4912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -114,6 +129,7 @@ export class RTCEncryptionManager implements IEncryptionManager { | |||
public leave(): void { | |||
this.transport.off(KeyTransportEvents.ReceivedKeys, this.onNewKeyReceived); | |||
this.transport.stop(); | |||
this.participantKeyRings.clear(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The legacy encryption manager was only clearing its own key here, but I don't see why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found the title of this PR a little confusing, as the ability to re-emit keys already existed and it hasn't changed substantially. Seems this is primarily about un-deprecating EncryptionManager.getEncryptionKeys
?
Follow up on #4799
Fixes https://github.com/element-hq/voip-internal/issues/375
After discussions
IEncryptionManager#getEncryptionKeys()
cannot be deprecated.There is a legit use case for the RTCSession beeing ready and running while the rtc app is not yet ready/started. That means that keys could be arriving already. Hence when the app is ready there should be a way to re-emit / access the keys.
Checklist
public
/exported
symbols have accurate TSDoc documentation.