8 ms·
While HTTPS is taking over web traffic, encrypted email could be considered a failure, at this point. I wonder what percentage of emails are encrypted using GPG
by oblio 9y ago
While HTTPS is taking over web traffic, encrypted email could be considered a failure, at this point. I wonder what percentage of emails are encrypted using GPG. Based on my experience it's probably less than 0.001%.
- zaarn 9y agoE-Mail needs better tools and better standards than GPG IMO. For one, GPG tools are difficult to use. Anything beyond a simple 1-click-setup-ready-to-use-including-keyserver-publication will make any wide market adoption difficult. On the other, the GPG standard is a bit ... clunky. Ideally it should be modernized to take advantage of the email format; add generic messages about encryption in alternate mime content bodies and simply encode the encrypted messages into it's own. I imagine other, similar, improvements could be made, up and including having GPG also sign the email headers before pushing it out into the world.
- AnaniasAnanas 9y agoGPG is not a standard, the standard is OpenPGP. As for the tools, they seem very easy, especially engimail which IS 1-click setup. > add generic messages about encryption in alternate mime content bodies and simply encode the encrypted messages into it's own This is exactly what it is doing. PGP/MIME is a thing.
- zaarn 9y agoEnigmail is far from friction free and no 1-click setup. I still have to go through key generation last I checked. And then publish those keys or give them to friends. If PGP/GPG wants adoption they need to eliminate those friction points, a TOFU model with automatic key redistribution should lower friction sufficiently but except TOFU there isn't much development in that direction. >This is exactly what it is doing. PGP/MIME is a thing. I don't think I ever received a single PGP/MIME email. I don't think a lot of people use PGP/MIME. It's a niche setting for a niche software.
- dane-pgp 9y agoYour desire for "a TOFU model with automatic key redistribution" is well-founded, and people (including implementers) are trying to do something about this. Check out the Autocrypt project: https://autocrypt.org/ https://autocrypt.org/ A similar (and complementary) approach is outlined in RFC-7929: https://tools.ietf.org/html/rfc7929 https://tools.ietf.org/html/rfc7929 which is supported by GPG and a few email providers.
- AnaniasAnanas 9y ago> no 1-click setup True, it is 3-click setup. > I don't think I ever received a single PGP/MIME email I haven't seen non-PGP/MIME emails in ages. In fact, Engimail uses PGP/MIME by default.
- cyphar 9y ago> the standard is OpenPGP The standard is PGP. OpenPGP is an implementation.
- AnaniasAnanas 9y agoIs this a joke?
- jwilk 9y agoNo. OpenPGP is the standard. PGP and GPG are implementations of this standard.
- lmm 9y agoBetter tools yes, better standards no. There isn't a single production-quality library implementation of the OpenPGP standard; anyone who uses OpenPGP in production ends up with some variant on a crappy 700-line python script wrapping the GPG executable. (There are dozens or hundreds of those out there, every company has their own). I'll never understand what possesses people who aren't up to writing a solid library implementation of the existing standard to believe that they would be capable of coming up with a better new standard, but it's distressingly common. Error reporting in email clients that support OpenPGP is awful because they all work by some variant of exec-ing the GPG process and piping its input/output, so half the time you'll try to set up PGP and it just won't work. Even when it does work, no extant mail program has yet reached the level of having an actual UI/UX designer spend even a couple of months of work actually trying to make the PGP experience a good one - and why would they when no-one's prepared to pay for it? Security professionals are willing to work for free on things like security audits of the GPG code, because you can get a conference paper out of that, but there's no corresponding channel for usability work. > Ideally it should be modernized to take advantage of the email format; add generic messages about encryption in alternate mime content bodies and simply encode the encrypted messages into it's own. PGP/MIME already does this. We don't need a new standard. We need to get better at using the standard we have.
- rakoo 9y agoTotally agree on it. Autocrypt (https://autocrypt.org/index.html https://autocrypt.org/index.html) is looking good as an incremental approach towards an automatic, widespread use of encryption in emails
- yrro 9y agoForgive me but isn't GPGME the high level library that programs probably want to use rather than dealing with gpg's protocol themselves?
- lmm 9y agoGPGME is a library that automates the exec-ing and pipeing, with all the issues that come with that (e.g. poor error reporting).
- simias 9y agoPGP and HTTPS have very different trust models so it's comparing apples to oranges. That being said I agree that PGP failed to gain widespread adoption even though I personally use GnuPG daily and sign all of my emails. I'm still hoping that it'll make a comeback but I'm not holding my breath.
- jcims 9y agoS/MIME uses a trust model similar to HTTPS, is built in to most clients and still has almost zero adoption. I think the issue is that HTTPS is a pain in the ass for a few, while encrypted email is a pain in the ass for everyone. Between client cert distribution to wonky webmail support to escrow challenges for regulated orgs it requires deliberate effort for all parties forever.
- simias 9y agoYeah S/MIME probably overlaps with HTTPS a lot these days, especially in corporate environment where it makes the most sense. Just setup an encrypted connection with the company's messaging platform and you're good. For personal email GPG is still pretty much the way to go if you don't want to trust any 3rd party though. Few people seem to care about that these days however. The fact that GPG's UI is abysmal doesn't help.
- pjc50 9y agoAs Let's Encrypt showed, this is all about usability.
- m_eiman 9y agoLet's encrypt wouldn't be nearly as widely used if browsers didn't require https for a lot of new features people want to use, though. And Google will lower the ranking of non-https sites soon, if they haven't already. Having Let's encrypt available as a free option lets the browser makers force web services to use https, since "anyone can add it, it's free! (Never mind the increased complexity and even more things that can fail and break things in weird ways)". I suppose it'd be harder to do something similar with email.
- moviuro 9y agoGoogle already pushes for encrypted-in-transit: https://blog.google/products/gmail/making-email-safer-for-you-posted-by/ https://blog.google/products/gmail/making-email-safer-for-yo...
- rocqua 9y ago/Donns alufoil hat Google likes HTTPS, it makes the web safer, and keeps middle-boxes from interfering with their stuf. However, Gmail likes access to the plaintext stuff. They no longer use email content for ad-targeting, but they still need this access for spam-filtering and auto labeling. Gmail is essentially e-mail for a lot of people, so what they do matters.
- arm 9y ago“However, Gmail likes access to the plaintext stuff. They no longer use email content for ad-targeting, but they still need this access for spam-filtering and auto labeling.” Absolutely. As mentioned in this¹ article: “Though Google announced that it would stop using consumer Gmail content for ad personalization last July, the language permitting it to do so is still included in its current privacy policy, and it without a doubt still scans users emails for other purposes. Aaron Stein, a Google spokesperson, told NBC that Google also automatically extracts keyword data from users’ Gmail accounts, which is then fed into machine learning programs and other products within the Google family. Stein told NBC that Google also “may analyze [email] content to customize search results, better detect spam and malware,” a practice the company first announced back in 2012.” ―――――― ¹ — https://theoutline.com/post/4524/remember-when-google-said-it-would-stop-reading-your-email https://theoutline.com/post/4524/remember-when-google-said-i...
- r3bl 9y agoHTTPS means encryption in transit. Email are also encrypted in transit (almost) universally. Encryption in transit has absolutely nothing to do with keeping the data hidden from the service you're visiting.
- rocqua 9y agoMy point exactly, google helped with the transition to HTTPS, but doesn't want to help the transition to encrypted email.
- endorphone 9y agoThe majority of email is encrypted in transit (https://transparencyreport.google.com/safer-email/overview?hl=en https://transparencyreport.google.com/safer-email/overview?h...), so from a third-party-watching perspective it is equivalent to HTTPS.