-
Notifications
You must be signed in to change notification settings - Fork 258
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
Support for secret storage (4S) #402
Comments
The secret storage account data event types have been partially implemented in last year's GSoC, |
The linked ruma issue is cloed now. Just wondering what the status of this is? |
As mentioned in #1065, no movement as of yet. |
Some movement now. PR adding support in the crypto crate: #2591. |
This has been now implemented as part of #2621. |
Secret storage allows us to store the private parts of our cross signing keys and our backup key on the server in the global account data storage box of our user.
This heavily relies on sending requests to the server and getting account data from the sync. Since the crypto crate can't send out requests nor does it have access to the account data it may make sense to just add helpers to the crypto crate and implement the rest of the logic in the top level crate.
Spec entry can be found here: https://spec.matrix.org/unstable/client-server-api/#secret-storage
The text was updated successfully, but these errors were encountered: