-
Notifications
You must be signed in to change notification settings - Fork 54
feat(llc): end-to-end encryption #1312
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
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
6339f2b
end-to-end encryption
Brazol 687eb2b
changelog
Brazol f80a48a
added encrypted badge
Brazol 4cfb09d
e2ee resolver for ringing
Brazol 8d71f9d
tweak
Brazol cd4885b
bump webrtc
Brazol 109c78d
Merge branch 'main' into feat/e2ee
Brazol 12dd810
fix
Brazol 69881cb
update macos project files
renefloor a9d56e0
fixes
Brazol f1bc0cb
unrecoverable error fix
Brazol a9decae
Merge branch 'main' into feat/e2ee
Brazol 58dfe3c
fixes
Brazol File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
Stream Video web demo join page end-to-end encryption key URL fragment or query parameter💡 Result:
Stream Video's SDK does not utilize URL fragment query parameters to handle or transmit end-to-end encryption (E2EE) keys [1][2]. Instead, the Stream Video SDK handles E2EE through a client-side EncryptionManager, which you must instantiate and attach to the call object before calling the join method [1][3]. The developer is responsible for generating the encryption key and sharing it with other participants through a secure channel of their own choosing (e.g., your application's backend or a secure signaling mechanism) [1][2]. Key implementation details include: - EncryptionManager: You create this manager using the current user ID and use methods such as setSharedKey to provide the encryption key directly to the SDK [1][3]. - Attachment: The EncryptionManager must be attached to the call instance using call.setE2EEManager prior to joining the call [1][2]. - Security: The SDK ensures that media frames are encrypted locally before being sent over the network, meaning Stream's infrastructure only processes and forwards encrypted ciphertext [1][3]. While some other third-party SDKs may offer varying methods for E2EE configuration, Stream Video's architecture intentionally separates key management from the transport layer to maintain control on the client side [1][3]. Using URL fragments for such purposes is generally considered a security risk and is not part of the Stream Video SDK's design.
Citations:
Sensitive Data Exposure (CWE-598)
Reachability: External · Exploitability: Moderate
Do not pass the passphrase in the URL query string.
The hosted Pronto join page expects
encryption_keyas a query parameter. A fragment-only SDK change will break web joins. Use an out-of-band key exchange, or update the hosted page and both native readers together.🤖 Prompt for AI Agents