Skip to content

MSC3735: Add device information to m.room_key.withheld message#3735

Open
uhoreg wants to merge 2 commits into
matrix-org:mainfrom
uhoreg:add_device_to_withheld
Open

MSC3735: Add device information to m.room_key.withheld message#3735
uhoreg wants to merge 2 commits into
matrix-org:mainfrom
uhoreg:add_device_to_withheld

Conversation

@uhoreg

@uhoreg uhoreg commented Feb 18, 2022

Copy link
Copy Markdown
Member

@uhoreg uhoreg changed the title MSCxxxx: Add device information to m.room_key.withheld message MSC3735: Add device information to m.room_key.withheld message Feb 18, 2022
@uhoreg uhoreg added A-Client Server Client-Server API A-Encryption E2EE 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. proposal-in-review labels Feb 18, 2022
@turt2live turt2live added the kind:maintenance MSC which clarifies/updates existing spec label Feb 23, 2022
Comment on lines +20 to +21
- `from_device`: the device ID of the device sending the `m.room_key.withheld`
message (this is the same field name used in key verification)

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.

worth noting that there is a sender_key property which maybe we could use for this, though tbh from_device is probably more convenient

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: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. Process state.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants