Skip to content

MSC4385: Pushing secrets to other devices - #4385

Open
uhoreg wants to merge 5 commits into
matrix-org:mainfrom
uhoreg:secret_send_without_requestid
Open

uhoreg wants to merge 5 commits into
matrix-org:mainfrom
uhoreg:secret_send_without_requestid

Conversation

@uhoreg

@uhoreg uhoreg commented Dec 3, 2025 •

Copy link
Copy Markdown
Member

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: Allowing m.secret.send without a prior m.secret.request MSC4385: Allowing m.secret.send without a prior m.secret.request Dec 3, 2025
@uhoreg uhoreg added A-Encryption E2EE proposal A matrix spec change proposal. Process state. A-Client Server Client-Server API 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 3, 2025

@turt2live turt2live Dec 3, 2025 •

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 (sender)
  • Client (receiver, preferably different from the sender)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

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.

mautrix-go implementation can be found in mautrix/go#551

@uhoreg uhoreg changed the title MSC4385: Allowing m.secret.send without a prior m.secret.request MSC4385: Pushing secrets to other devices Dec 8, 2025
@uhoreg uhoreg added the kind:feature MSC for not-core and not-maintenance stuff label Dec 8, 2025
Comment thread proposals/4385-secret-send-without-requestid.md Outdated
uhoreg and others added 2 commits June 30, 2026 09:38
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
@giomfo

giomfo commented Jul 28, 2026

Copy link
Copy Markdown
Member

@uhoreg can we consider the implementations are done for this MSC?

@uhoreg

uhoreg commented Aug 6, 2026

Copy link
Copy Markdown
Member Author

@uhoreg can we consider the implementations are done for this MSC?

yes

@github-project-automation github-project-automation Bot moved this to Tracking for review in Spec Core Team Workflow Aug 7, 2026
@turt2live turt2live moved this from Tracking for review to Proposed for FCP readiness in Spec Core Team Workflow Aug 7, 2026
@tulir tulir removed the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Aug 20, 2026
@giomfo

giomfo commented Sep 22, 2026 •

Copy link
Copy Markdown
Member

@uhoreg @turt2live Hi, what is missing to get this MSC merged?

@uhoreg

uhoreg commented Oct 13, 2026

Copy link
Copy Markdown
Member Author

@uhoreg @turt2live Hi, what is missing to get this MSC merged?

It's just waiting for the SCT to have time to look at it. The SCT has been focusing on Matrix 2.0 MSCs recently, so they haven't been looking at anything else.

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 proposal A matrix spec change proposal. Process state.

Projects

Status: Proposed for FCP readiness

Development

Successfully merging this pull request may close these issues.

5 participants