Figure out E2EE for state events. #878
Labels
A-Client-Server
Issues affecting the CS API
feature
Suggestion for a significant extension which needs considerable consideration
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.
The text was updated successfully, but these errors were encountered: