News for hackers. Stuff that matters.
Re:The Ecosystem Is Moving [video] by Glosster on Sunday December 29, 2019 @04:13AM (#21904972)
Why is he saying that email is not encrypted? Isn't it actually encrypted when traveling from server to client? Who uses ports without SSL or TSL anymore?
Re:The Ecosystem Is Moving [video] by Glosster on Sunday December 29, 2019 @04:19AM (#21904997)
And why does it matter if WhatsApp offers encrypted chat, if they can just update their client tomorrow and make it so that their servers snoop on everything (if that's not already the case)? A lot of the arguments of this guy seem to also be useful against himself. I won't go into more detail.
Re:The Ecosystem Is Moving [video] by Ninn on Sunday December 29, 2019 @04:16AM (#21904985)
He is referencing end to end encryption. Google can see Your to/from/subject/metadata headers even if you bother to use gpg
Re:The Ecosystem Is Moving [video] by Glosster on Sunday December 29, 2019 @04:20AM (#21905000)
Then that's a problem with us using a centralized system (Google) for emails, right? So email is not really decentralized.
Re:The Ecosystem Is Moving [video] by cyphar on Sunday December 29, 2019 @05:45AM (#21905240)
Replace "Google" with "your email provider". Even if there were many diverse email providers with significant adoption, the problem would remain.

Unless you're using PGP (and -- critically -- the other people know how to use it as well), then your email is stored as plaintext on your email provider's email server (and the email provider of anyone you send the email to, as well as any forwarding agents that passed the email along).

Re:The Ecosystem Is Moving [video] by rakoo on Sunday December 29, 2019 @08:06AM (#21905694)
PGP alone is no longer sufficient to talk about encryption in emails. The real step up is autocrypt (https://autocrypt.org/) that encrypts almost everything. Unfortunately the way email works it is still possible to know who is talking to who.
Re:The Ecosystem Is Moving [video] by waldfee91 on Sunday December 29, 2019 @07:59AM (#21905675)
You could encrypt subject, from field and most metadata (some mail servers don't accept garbled from fields though). To field can not be encrypted, but that's the same on Signal (the server needs to know where to deliver the message to).
Re:The Ecosystem Is Moving [video] by ekianjo on Sunday December 29, 2019 @05:34AM (#21905196)
Nothing prevents you from not using Gmail.
Re:The Ecosystem Is Moving [video] by cyphar on Sunday December 29, 2019 @05:46AM (#21905246)
If any of the people you are communicating with are using an email provider that they don't personally host, then the problem is exactly the same. In fact, arguably a better comparison to E2EE is that they have to host an email server on each of their devices (which precisely zero people do).
Re:The Ecosystem Is Moving [video] by ekianjo on Sunday December 29, 2019 @09:33PM (#21910321)
Not at all. As long as your keys to decrypt messages are on your device only, the body of the message will be gibberish for your email host. You could argue that metadata is in jeopardy since the email recipient is not obfuscated but that is the same thing with Signal where you rely on a central server with phone numbers connecting people to each other's.
Re:The Ecosystem Is Moving [video] by cyphar on Sunday December 29, 2019 @10:21PM (#21910554)
> As long as your keys to decrypt messages are on your device only, the body of the message will be gibberish for your email host.

The original comment didn't imply usage of PGP. They asked whether messages being encrypted between mail hosts counted as E2EE -- and remember that the number of email users who also use PGP is close to 0%.

But with PGP, sure -- though PGP has many other problems which make it a questionable choice unless you are forced to use email for some other reason:

* Most email clients don't know how to use it and will often allow you to accidentally reply to an encrypted email with clear-text. This comes back to "every single one of the recipients of your email needs to actively know how to use it correctly".

* PGP doesn't have perfect forward secrecy (instead depending on long-lived keys) which means your entire conversation history is threatened if your keys ever become compromised.

* Most PGP implementations are not using properly-authenticated cryptography (yeah, there's the MDC but Efail showed that there were serious bugs in its design -- and backwards compatibility made it bypassable). OpenPGP still hasn't standardised AEAD.