-
Notifications
You must be signed in to change notification settings - Fork 379
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
Proposal for storing megolm keys serverside #1219
Comments
The API was designed for option 1, and mostly works for option 2, but it seems like the I think one way to support that is to have the client use the I think most of this (other than uploading other signatures) can be done with the existing API by changing the contents of the auth_data. |
@mscbot fcp merge |
Team member @uhoreg has proposed to merge this. The next step is review by the rest of the tagged people: No concerns currently listed. Once at least 75% of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. |
This issue should remain open because it is under the legacy process - we'll close it when the spec PR has been merged. |
@uhoreg if you have proofs of implementation, please link to them here. |
Synapse implementation: mainly in matrix-org/synapse#4019, with some bits in matrix-org/synapse#4123, matrix-org/synapse#4580, matrix-org/synapse#6189, and matrix-org/synapse#5858 (the last one needs a bit of tweaking yet) |
Spec PR: #2387 |
Merged! 🎉 |
Documentation: #1538
Author: @ara4n, @uhoreg
Date: 23/11/2017
The text was updated successfully, but these errors were encountered: