-
Notifications
You must be signed in to change notification settings - Fork 385
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
MSC1946: Secure Secret Storage and Sharing #1946
Conversation
uhoreg
commented
Mar 28, 2019
•
edited by richvdh
Loading
edited by richvdh
- Rendered as originally completed FCP
- As updated by MSC2472
@mscbot fcp merge |
Team member @uhoreg has proposed to merge this. The next step is review by the rest of the tagged people: Concerns:
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The first half of the proposal is hard to follow without more complete examples. There's a lot of new m.*
things being introduced, and it's not entirely clear how they all fit together.
@mscbot concern Unclear on how the stuff looks in object form |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
|
||
Example: | ||
|
||
Some secret is encrypted using keys with ID `key_id_1` and `key_id_2`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It’s unclear how the key_id_X relates to the [key ID] above. can the json example include the event details so we can see how it looks in account_data?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have added to the example
Co-Authored-By: Matthew Hodgson <matthew@arasphere.net>
FYI, I've just made a little tweak by making the |
hello @mscbot |
The final comment period, with a disposition to merge, as per the review above, is now complete. |
Merged! 🎉 |
Per matrix-org/matrix-spec-proposals#1946 and matching internal glossary
For links, note that this MSC was updated by MSC2472 after it completed FCP. |