Skip to content

Conversation

@uhoreg
Copy link
Member

@uhoreg uhoreg commented Dec 8, 2025

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.

@uhoreg uhoreg changed the title MSCxxxx: Automatically sharing secrets after device verification MSC4386: Automatically sharing secrets after device verification Dec 8, 2025
@uhoreg uhoreg added e2e proposal A matrix spec change proposal client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal-in-review labels Dec 8, 2025
Copy link
Member

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"]
Copy link
Contributor

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?
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client-server Client-Server API e2e kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal proposal-in-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants