End to end encryption
End to end encryption so that chats are secure and private. Obviously only enabled under certain circumstances and for certain groups/users but it is necessary for sensitive discussions around legal or security matters, ie sharing passwords.
Anton Volkov commented
You can't really say a product is secure until it has E2EE support. Please make it available in Teams, at least as a Private Chat feature, like private tab in browsers.
Nice post!If facing any inconvenience with respect to the Printer you can visit our site https://www.brotherprintersupport247.com/blog/brother-hl-l2340dw-wifi-setup/
need E2EE, keybase is a pain to manage :)
End to end should include the stored content not just the transport, HTTPS. So some sort of closed group shared key would be an example, so a sys-admin can not access the stored chat conversations for sensitive matters.
Yes, end to end encryption is a must.
Bryan Letcher commented
Slack does not seem to care. End to end encryption should matter to everyone who wants a secure messaging platform.
J. Warwick commented
I'd be interested at least in a diagram that illustrates all the involved connections. I would imagine absolutely everything that Teams client does is through HTTPS connections. Does that count as "end to end"? That doesn't cover, at least, "data at rest" .
I voted up any way, though this may be satisfied with just a well documented and well communicated statement that "hey guys, we already have that! its built-in!" if that is really so.