-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
configuration flag to enable encryption by default in new rooms #2431
Comments
this already exists on the dinsic branch; needs to be ported to develop |
c.f. #3426 This is more important given Riot is now e2ee by default, and folks expect the server to have the option to enforce this. |
Is this only for private rooms? The issue says any new room, whereas the linked PR only acts on private rooms. I'm going to write a PR atm assuming we want private-only. |
People have expressed that they would like to have the option between:
As a config option design, this could be two options - one for public and one for private, however I feel that's not very future-proof. Instead, I'm thinking of:
Sound plausible? |
Discussions in #synapse-dev were positive. PR now has the updated format. |
Fixes #2431 Adds config option `encryption_enabled_by_default_for_room_type`, which determines whether encryption should be enabled with the default encryption algorithm in private or public rooms upon creation. Whether the room is private or public is decided based upon the room creation preset that is used. Part of this PR is also pulling out all of the individual instances of `m.megolm.v1.aes-sha2` into a constant variable to eliminate typos ala #7637 Based on #7637
You missed the biggest recent requested option since riot forced e2ee on.
|
To force everyone on the server to use it.
The text was updated successfully, but these errors were encountered: