-
Notifications
You must be signed in to change notification settings - Fork 2
Add Extra End-to-End Encryption Layer (beyond WebRTC) #75
Copy link
Copy link
Open
Labels
clientChanges made for the Client sideChanges made for the Client sidedependenciesPull requests that update a dependency filePull requests that update a dependency filedocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestfeatureCreating a new featureCreating a new featurejavascriptPull requests that update javascript codePull requests that update javascript codetypescriptPull requests that update TypeScript codePull requests that update TypeScript code
Description
Metadata
Metadata
Assignees
Labels
clientChanges made for the Client sideChanges made for the Client sidedependenciesPull requests that update a dependency filePull requests that update a dependency filedocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestfeatureCreating a new featureCreating a new featurejavascriptPull requests that update javascript codePull requests that update javascript codetypescriptPull requests that update TypeScript codePull requests that update TypeScript code
Projects
Status
backlog
Is your feature request related to a problem? Please describe.
While WebRTC already provides built-in encryption, we want to add an extra layer of end-to-end encryption (E2EE) for data shared within the project. This added security will help protect sensitive information even if the standard transport encryption is compromised.
Describe the solution you'd like
Implement an additional end-to-end encryption layer for all data shared through the platform, beyond the default WebRTC encryption. This could involve encrypting data before it is sent and decrypting it only after receipt, using user-controlled keys or session-based encryption. Ideally, this should be transparent to users but configurable for advanced use cases.
Describe alternatives you've considered
Additional context
Consider compatibility with current WebRTC flows and make sure the implementation does not degrade performance or user experience. Provide clear documentation for users on how additional E2EE works and its benefits.