-
Notifications
You must be signed in to change notification settings - Fork 29
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
#254: Address key material sharing consistently #256
Conversation
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 editorial changes at the beginning of this PR make sense. The substantive changes seem like regressions and I don't think we should make them. If you want to narrow the PR as indicated in the review I'll land it.
draft-ietf-mls-architecture.md
Outdated
provide a synchronization mechanism so that the clients' state remain consistent | ||
across changes to the MLS group. Flaws in this synchronization mechanism may | ||
impair the ability of the user to recover from a compromise of one of their | ||
devices. |
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.
This text looks good, but I think you need to reinstate the previous text somewhere:
An attacker could use one compromised device to establish ownership of a state across other devices and reduce the ability of the user to recover.
No description provided.