What end-to-end encryption should look like

Re:What end-to-end encryption should look like by hathawsh on Wednesday April 22, 2020 @06:36PM (#22950964)

I like that idea. I think there might be some risk that because all recipients receive the same encrypted text (encrypted by a different key for each recipient), a recipient may be able to discover other recipients' encryption keys. To avoid that, I think I would pad each encrypted text with random data, where each recipient gets different random data.

Then the problem boils down to key management, but Keybase has that figured out IMHO. :-) It would be amazing to see a collaboration between Jitsi and Keybase to build end-to-end encrypted video chat with high quality crypto.

[ Parent | on HN ]

Re:What end-to-end encryption should look like by danenania on Wednesday April 22, 2020 @09:09PM (#22951846)

"I think there might be some risk that because all recipients receive the same encrypted text (encrypted by a different key for each recipient), a recipient may be able to discover other recipients' encryption keys."

If that's possible, it means you're using horribly broken encryption. So it shouldn't be a concern if you're doing things right.

[ Parent | on HN ]

Re:What end-to-end encryption should look like by hathawsh on Wednesday April 22, 2020 @09:41PM (#22952018)

Yeah, on second thought, that would mean TLS is broken: if many people connect to a static web site and receive the same content, they would be at risk of revealing key material. However, they are not at risk of any such thing. Never mind. :-)

[ Parent | on HN ]