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

Cannot enable E2E on public channels #12417

Open
ghost opened this issue Oct 25, 2018 · 3 comments
Open

Cannot enable E2E on public channels #12417

ghost opened this issue Oct 25, 2018 · 3 comments

Comments

@ghost
Copy link

ghost commented Oct 25, 2018

This seems to be done on purpose, shown here: https://github.com/RocketChat/Rocket.Chat/blob/develop/packages/rocketchat-channel-settings/server/methods/saveRoomSettings.js#L76

...why? There's not that large of a difference between a private and public channel.

@localguru
Copy link
Contributor

Anyone can access a public channel, so the messages there are public and do not need to be encrypted from Rocket.Chat's point of view. But from a hosting point of view this can make sense, e.g. if the service is operated in a cloud. Because even then you don't want these messages to be read by the cloud operator, but by all Rocket.Chat users. In this respect I think that there are also cases in which public channels should be encrypted.

@ghost
Copy link

ghost commented Nov 2, 2018

Yeah, E2E encryption for public channels would be really awesome.

@tiagoefreitas
Copy link

Public only means its accessible by all users of the server, it has nothing to do with security.
If we want security for all users and all conversations, then E2E should be used for everything by default, like Whatsapp and Signal do.
Encryption should be as much invisible to the users as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants