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

Option to disable encryption for local DMs #3351

Open
alex9434 opened this issue Apr 2, 2024 · 3 comments
Open

Option to disable encryption for local DMs #3351

alex9434 opened this issue Apr 2, 2024 · 3 comments

Comments

@alex9434
Copy link

alex9434 commented Apr 2, 2024

Description:

I suggest to enable a setting in dendrite.yaml to have all DMs between users on the local server unencrypted by default. DMs to users on other servers should be encrypted by default.

Rationale: Chats between local users are only stored on the local server and therefore can be protected on the server level. Encryption adds unnecessary overhead (e.g. using multiple devices) and also makes it impossible to audit/document chats for companies.

@S7evinK
Copy link
Contributor

S7evinK commented Apr 3, 2024

This is more about the client sending the create event. Dendrite doesn't choose to encrypt or not.

Disabling E2EE while the UI shows that it's going to be an encrypted chat feels wrong.

@alex9434
Copy link
Author

alex9434 commented Apr 4, 2024

My assumption was that Dendrite would be the best to understand whether this the DM is created between two local users. The client might not know whether the user is local or via federation. My proposal would not be to show in the UI the chat is encrypted while in reality it is not. Instead I suggest a configuration setting (e.g. overwrite encryption request for local DMs) that converts a request from a client to create an unencrypted DM if both users are local on the server. The client would then show that the DM is unencrypted.

@0x00cl
Copy link

0x00cl commented Apr 20, 2024

This doesn't make much sense. End-to-end encryption makes sure only the sender and the reciever can write/read messages. So not even your homeserver should read/modify your messages. That isn't unnecessary overhead.

Also from my understanding this is not a server related option.

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

3 participants