Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a config option to block local users from enabling encryption in a room #17307

Open
Twi1ightSparkle opened this issue Jun 14, 2024 · 0 comments

Comments

@Twi1ightSparkle
Copy link
Contributor

Description:

There are use cases where you do not want encryption enabled in any of your rooms. You can sort-of achieve this today using your well-known files, however this is more of a suggestion to clients and may not always be reliable for example if the file is temporarily unavailable or the client fails to read it for any reason.

Therefore, Synapse should have an option to block all local users from setting the encryption state events in any room. I suggest a new Synapse configuration option that is of course disabled by default. Alternatively, add a new option, (block or never for example) on encryption_enabled_by_default_for_room_type.

For completeness, this block policy should apply both on room creation and for enabling encryption in the room later.

It should however probably not block users from joining existing local or federated encrypted rooms.

@Twi1ightSparkle Twi1ightSparkle changed the title Draft: Add a config option to block local users from enabling encryption in a room Add a config option to block local users from enabling encryption in a room Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant