MSC4261: "Do not encrypt for device" flag #4261
Open
Conversation
This file contains 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
uhoreg
changed the title
uhoreg
added
e2e
proposal
uhoreg
commented
Feb 1, 2025
|
|
||
| ## Proposal | ||
|
|
||
| A new optional `do_not_encrypt` property is added to the `DeviceKeys` structure |
There was a problem hiding this comment.
Suggestions for better names welcome
turt2live
reviewed
Feb 2, 2025
There was a problem hiding this comment.
Implementation requirements:
- Client asking to not be encrypted to
- Client not encrypting to that other client
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.
Rendered
Conflict of interest statement: I am a Matrix Spec Core Team member, and and employee of Element on the Cryptography team. This proposal was written as part of my work on the Element Cryptography team, based on feedback on MSC4153.