MSC4153: Exclude non-cross-signed devices #4153
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
uhoreg
changed the title
uhoreg
added
e2e
proposal
turt2live
reviewed
Jun 10, 2024
There was a problem hiding this comment.
Implementation requirements:
- Client embodying these values (preferably cross platform).
There was a problem hiding this comment.
I believe that EW and EX both implement this, via their respective labs flags.
EW's setting looks like this:
deepbluev7
reviewed
Jun 10, 2024
richvdh
reviewed
Jun 12, 2024
This was referenced Jun 13, 2024
Closed
dkasak
reviewed
Jun 13, 2024
This was referenced Jun 17, 2024
uhoreg
changed the title
poljar
pushed a commit
to matrix-org/matrix-rust-sdk
that referenced
this pull request
Jul 3, 2024
This sharing strategy is defined as part of MSC4153[1]. [1]: matrix-org/matrix-spec-proposals#4153
tulir
reviewed
Jul 26, 2024
foresto
reviewed
Sep 17, 2025
Co-authored-by: Andrew Morgan <[email protected]> Co-authored-by: Travis Ralston <[email protected]> Co-authored-by: Patrick Cloke <[email protected]> Co-authored-by: Alexey Rusakov <[email protected]>
|
@mscbot resolve Guidance to clients on how to create cross-signing keys (links to spec, conflict resolution, etc) |
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
mscbot
added
final-comment-period
turt2live
removed
the
00-weekly-pings
Johennes
reviewed
Oct 1, 2025
Johennes
reviewed
Oct 1, 2025
Johennes
reviewed
Oct 1, 2025
Johennes
reviewed
Oct 1, 2025
Johennes
reviewed
Oct 1, 2025
turt2live
added
kind:core
|
The final comment period, with a disposition to merge, as per the review above, is now complete. |
mscbot
added
finished-final-comment-period
and removed
disposition-merge
final-comment-period
|
(this MSC is being held in its current state pending resolution of #4153 (comment) ) |
to be compatible with suggestion to delay implementation
That thread is now resolved, and this MSC is now considered to have properly finished FCP. |
turt2live
added
spec-pr-missing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
23 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered
Conflict of Interest declaration: I am a member of the Spec Core Team, and am employed by Element. This MSC was written as part of my work on the Element Cryptography team.
SCT Stuff:
MSC checklist
FCP tickyboxes