You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once that's done, we'll need to harmonise the specs in terms of signature-related event properties and add some technical details and advices on signature generation.
I'm wondering whether this is really needed at a specifications level. The current structure we have is good enough regardless of whether we use the Matrix SDKs to handle signing events, so surely we can go with it and decide what the implementation looks like once we start working on it?
Riot uses device keys in order to encrypt events in E2E encrypted rooms. These keys are also able to sign events.
Can we use the Matrix key infrastructure for generating cryptographic keys and use them for signing events (without encrypting them) ?
Matrix E2E spec: https://matrix.org/speculator/spec/HEAD/client_server/unstable.html#module-e2e
The text was updated successfully, but these errors were encountered: