Repository navigation
feat(security): add end-to-end encrypted sharing - #291
Open
ThisIs-Developer wants to merge 1 commit into
Open
ThisIs-Developer wants to merge 1 commit into
ThisIs-Developer wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds end-to-end encryption for newly created Share Snapshots, managed attachments, and Live Share rooms to strengthen content privacy. Encryption and decryption run on the device; complete share-link fragments carry the keys, which are never sent to the storage or relay APIs.
Validation:
npm run buildand the full unit suite passed (272 tests), followed by 14 focused encryption/real Cloudflare relay checks after final cache hardening. All 14 targeted Chromium browser tests passed, covering actual local Miniflare/Yjs collaboration, snapshot compatibility and missing keys, encrypted media/export, private rendering, Review feedback, split-view/native uploads, and startup. Desktop resource preparation and final static checks passed.npm auditreported zero vulnerabilities.Rollout requires the updated Durable Object Worker, Pages Functions, and browser assets together; older clients should refresh before creating new shares. Existing links keep their original lifetime. Complete links remain bearer credentials, and operational metadata and recipient copies are outside the encryption boundary. Details are in
docs/ENCRYPTED_SHARING.md.