Skip to content

MSC4483: Encrypted Account Data#4483

Open
thetayloredman wants to merge 2 commits into
matrix-org:mainfrom
thetayloredman:encrypted-account-data
Open

MSC4483: Encrypted Account Data#4483
thetayloredman wants to merge 2 commits into
matrix-org:mainfrom
thetayloredman:encrypted-account-data

Conversation

@thetayloredman

@thetayloredman thetayloredman commented May 25, 2026

Copy link
Copy Markdown

Signed-off-by: Logan Devine <logan@zirco.dev>
Signed-off-by: Logan Devine <logan@zirco.dev>
@thetayloredman thetayloredman changed the title MSCXXXX: Encrypted Account Data MSC4483: Encrypted Account Data May 25, 2026
Comment on lines +73 to +74
investigated in the Matrix ecosystem, and if it is determined that these algorithms are ineffective, a future MSC may
introduce additional algorithms.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am unsure how to introduce forward-compatibility in this MSC directly as it is very possible the preferred algorithm will change in the future. To my understanding, secrets within SSSS lack any form of key ID (only the root keys do), so the algorithm of the ADK would need to be specified somehow.

@turt2live turt2live added A-Encryption E2EE proposal A matrix spec change proposal. Process state. A-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. labels May 25, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Client (setting)
  • Client (reading)

Comment on lines +63 to +66
* Eliminate the ADK and simply use the SSSS master.
Using the SSSS master would require re-encrypting account data whenever recovery keys change. Usage of a separate ADK
is extensible for further `account_data` events, alongside providing the ability to rotate the ADK independently of
SSSS.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additionally using the "SSSS master" would require clients to keep its private part stored which, I think, many clients currently don't do?

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

Labels

A-Client Server Client-Server API A-Encryption E2EE 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. Process state.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants