Skip to content

MSC4312: Resetting cross-signing keys in the OAuth world #4312

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Johennes
Copy link
Contributor

@Johennes Johennes commented Jul 15, 2025

@Johennes Johennes changed the title MSCXXXX: Resetting cross-signing keys in the OAuth world MSC4312: Resetting cross-signing keys in the OAuth world Jul 15, 2025
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
@Johennes Johennes force-pushed the johannes/x-signing-reset-with-nextgen-auth branch from cc0517c to e78bc09 Compare July 15, 2025 08:20
@Johennes Johennes marked this pull request as ready for review July 15, 2025 08:21
@turt2live turt2live added proposal A matrix spec change proposal client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Jul 15, 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:

  • Server
  • Unsupporting client
  • Supporting client

Copy link
Contributor Author

@Johennes Johennes Jul 16, 2025

Choose a reason for hiding this comment

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

Server: element-hq/synapse#17509 (July 2024)
Supporting client: element-hq/matrix-react-sdk#34 (September 2024)

I'm not sure how an unsupporting client would be implemented. They'd simply use the UIA fallback mechanism without any changes needed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants