-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
prune_event
strips keys needed for authentication from events.
#1831
Comments
prune_event
strips third_party_invite
keys from membership events.prune_event
strips keys needed for authentication from events.
I think this will be fixed by #8984, if/when it ever makes it into a production room version. |
It looks like that PR/MSC only fixes things for the |
mmm, true |
as matrix-org/matrix-spec-proposals#2176 (comment) says, MSC2176 doesn't fix #8984 does fix |
I've started an MSC2176 2.0 to handle |
Note that #15563 implements MSC3821. So (assuming the MSC is accepted) we should be able to close this when that's released in a room version. |
It looks like we've been using keys in the event authentication checks without making sure they won't be removed when an event is redacted:
third_party_invite
JSON keys in invitem.room.member
event content.(fixed by msc2716, Implement MSC2176: Updated redaction rules #8984)redacts
JSON keys inm.room.redaction
events(fixed by msc2716, Implement MSC2176: Updated redaction rules #8984)m.federate
JSON keys inm.room.create
eventshttps://github.com/matrix-org/synapse/blob/v0.18.7/synapse/events/utils.py#L41-L57
https://github.com/matrix-org/synapse/blob/v0.18.7/synapse/events/utils.py#L69
https://github.com/matrix-org/synapse/blob/v0.18.7/synapse/events/utils.py#L71
Unfortunately fixing this will break the event signature checks for those events.
The text was updated successfully, but these errors were encountered: