Skip to content
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

Figure out E2EE for state events. #878

Open
ara4n opened this issue Aug 8, 2021 · 3 comments
Open

Figure out E2EE for state events. #878

ara4n opened this issue Aug 8, 2021 · 3 comments
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration

Comments

@ara4n
Copy link
Member

ara4n commented Aug 8, 2021

The human-readable bits of state events (i.e. the bits that a redaction would apply to) should be encryptable using at least a static key, which could be shared around the room between clients. The same static key could be used for basic non-ratchet E2EE in massive rooms. Somehow we seem to lack a bug for this, so: here we are.

@aaronraimist
Copy link
Contributor

@ara4n
Copy link
Member Author

ara4n commented Aug 8, 2021

oh, yes. doh.

@ara4n ara4n transferred this issue from matrix-org/matrix.org Aug 8, 2021
@MadLittleMods MadLittleMods added A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration labels Aug 9, 2021
@ara4n
Copy link
Member Author

ara4n commented Nov 22, 2021

matrix-org/matrix-spec-proposals#3414

@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration
Projects
None yet
Development

No branches or pull requests

3 participants