-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Upgrading a public room erroneously makes it E2EE when E2EE is required for private rooms #9246
Comments
Not required per se, but |
This setting isn't actually used by Synapse, it just gets passed through to the clients in the |
Actually, we do use those config options when generating a room, so the ball may in fact be in Synapse's court: synapse/synapse/handlers/room.py Lines 106 to 112 in 9dde9c9
The default value is synapse/synapse/handlers/room.py Lines 435 to 445 in 9dde9c9
We note that the preset setting is quite arbitrary, as we'll overlay the state from the previous room. We could solve this specific case by switching the preset from PRIVATE to PUBLIC, though I think a better solution would just be to create a room without any state other than the bare minimum - then overlay the old room's relevant state on top. |
That would be a better solution for upgrades. However having looked at this a bit more since posting my first reply, this is clearly a bug that affects more than just room upgrades. Creating any sort of private room in Element with this setting set to to |
@jonaharagon Hrm, you're right. Clients can only indicate that they want encryption by sending Turning this option on will add a |
Since Issue #14719 was determined to be a duplicate of this issue, I am proposing that the Also this issue might need a title revision as public & private rooms can BOTH be E2EE. |
Description
(Note: I'm filing this issue on behalf of someone else, who can't currently file issues, so I don't have direct access to the homeserver in question.)
When Synapse is configured to require E2EE for private rooms, then when a public room is upgraded through that homeserver, it is erroneously marked as end-to-end encrypted. According to TravisR:
Automatically enabling E2EE for the upgraded room should only occur for private rooms, instead.
Steps to reproduce
/upgraderoom 6
in Element Web/DesktopVersion information
If not matrix.org:
Version: unknown
Install method: unknown
The text was updated successfully, but these errors were encountered: