-
Notifications
You must be signed in to change notification settings - Fork 424
MSC4386: Automatically sharing secrets after device verification #4386
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
base: main
Are you sure you want to change the base?
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.
Implementation requirements:
- Sending client
- Receiving client (ideally different from the sending one)
| "m.cross_signing.self_signing", | ||
| "m.cross_signing.user_signing" | ||
| ], | ||
| "requested": ["org.example.custom"] |
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.
Wouldn't DEVICEB already know that DEVICEA cannot provide this secret based on the earlier verification request?
|
|
||
| ## Potential issues | ||
|
|
||
| None? |
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.
When using in-room verification, I think, you could theoretically run into the 64KiB event size limit? Secrets stored in account data won't be subject to this limit. Even if they were, you could exceed it because multiple secrets are combined in a single m.key.verification.secrets event.
This is probably not a practical problem because secrets should normally be relatively small. So I'm not sure if we really need to do anything. Maybe a dedicated error code at most?
Rendered
Disclosure: I am a member of the Element crypto team, and of the Spec Core Team. This proposal is written as a member of the Element crypto team.