An Update to End-To-End

Re:An Update to End-To-End by sft on Tuesday December 16, 2014 @05:10PM (#8759899)

I wish they would stop calling it End-to-End, it's misleading, they don't talk about DNS at all. One weak link in the chain means the entire chain is weak.

[ Parent | on HN ]

Re:An Update to End-To-End by notatoad on Tuesday December 16, 2014 @07:07PM (#8760375)

DNS is not relevant at all here. Your email is encrypted client-side at one end, and decrypted client-side at the other end. At no point in between does it exist in cleartext. If there is some DNS vulnerability that causes your email to get intercepted, that in no way compromises the encryption.

[ Parent | on HN ]

Re:An Update to End-To-End by sft on Wednesday December 17, 2014 @02:36PM (#8763860)

Here? Where is here? The blog mentions nothing about email specifically.

[ Parent | on HN ]

Re:An Update to End-To-End by notatoad on Wednesday December 17, 2014 @03:42PM (#8764220)

Whatever. "here" is any text encrypted by this module, whether it is the body of an email or something else. The data isn't getting decrypted mid-stream, it goes from one client (or "end") to another. It is end to end encryption, and DNS has nothing to do with it.

[ Parent | on HN ]