3 ms·
1. Google probably should offer passive S/MIME on mail. START TLS goes a long way, but providing the same signals about message authenticity to people who IMAP
by rdl 13y ago
1. Google probably should offer passive S/MIME on mail. START TLS goes a long way, but providing the same signals about message authenticity to people who IMAP from gmail as who use the web UI would be nice.
A non-google-trusting way to do PGP with a better UI/UX would also be a nice feature for gmail. Just indicating "encrypted" at the message-list view or something. I have PGP working quite nicely in mutt, but a lot of people seem to prefer webmail.
2. I'd actually prefer a world where signals intelligence, outside extremely tactical intelligence, were impossible through technical means. I think we'll be there at some point, just because the cost of protection is dropping.
(confidentiality and message integrity should be feasible for any reasonable government defender at this point. traffic analysis/direction finding/etc. burns bandwidth and latency budgets, so that might be harder, but you can do arbitrarily well.)
The US (government and citizens/private industry) probably has more to gain from universally strong COMSEC vs. effective USG SIGINT.
- tptacek 13y agoI think I might prefer that world too. Now: how likely are we to be in that world any time soon?
- rdl 13y agoI'd bet "before 2025", absent some major catastrophe. First you build systems which let platform developers centralize trust, then the essential step is letting individuals or organizations pick their own roots of trust (and some kind of crazy web of trust thing for interchange). We're doing a pretty good job on mobile of "centralized trust", and also sort of with cloud infrastructure, if not apps. At least, we'll have secure infrastructure on which people can continue writing insecure applications by 2020-2025. The "people writing insecure applications" won't stop until people stop writing applications, hopefully replaced by non-humans writing applications, maybe in 2050+.
- mpyne 13y agoEverytime I think about the S/MIME and PGP issue I can't get away from the fact that you need to give your private key to the client-side JS. I'm not sure we've found all the security flaws we'll find in the browser JS model so that just seems risky to me (especially for digital signature purposes). And as you mention, you would still have to trust Google.
- rdl 13y agoW3C webcrypto, done in a smart way, is probably one of the most critical pieces of security infrastructure to be built today. I'm not talking about giving the real PGP or S/MIME to Google; just a UI flag saying "this message has special content, click here to download". And some kind of low-assurance S/MIME signature which just says "was downloaded from gmail" to protect from local modification. I'm not sure how mail clients deal with multiple s/mime signatures (or s/mime + PGP inside).
- tptacek 13y agoIt's not being done in a particularly smart way; Web Crypto has more to do with enabling pure-web plugin-free streaming media than with enabling secure browser-based PGP.
- rdl 13y agoPresumably all it would take would be Google, Apple, or even Mozilla to do something more real on their own. I'd probably bet on the Chrome doing it more than anyone else.
- blake8086 13y agoI think you're thinking of Encrypted Media Extensions https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
- tptacek 13y agoNo, I'm thinking about the design decisions the Web Crypto team made and the mailing list posts that supported them.
- X-Istence 13y agoSTARTTLS is supported on both IMAP/SMTP. Email from Google outgoing uses TLS encryption (at least to my mail server), email from my server to Google also uses TLS encryption. IMAP is already TLS encrypted. The biggest missing puzzle piece is making it simpler for people to get S/MIME set up (or PGP for that matter), and having it work with all major mail clients (yes, Mail.app is a major mail client). Right now S/MIME still requires too many steps to get the lay person to set it up, same with PGP, we need something that is secure from the get-go with very minimal effort required on the users part. The downside is that S/MIME and PGP don't really fit into the online world, no longer will it be simple to open the browser and go look at your email, you will be required to have your keys with you. Securing those keys becomes the second problem, one that has partially been solved with smart cards and other devices that will do signing/encrypting/decrypting on the card without giving up the private key... but loss is still an issue so key escrow becomes a big thing. It is an interesting problem, with interesting challenges and I look forward to seeing how we as a group of technologists solve them. Once it becomes easy enough for grandma and grandpa to use secure encrypted communication it will become much harder to do wide-scale snooping on data.
- rdl 13y agoThe lowest hanging fruit is probably a simple way to get S/MIME certs for mail.app (osx/ios). There isn't really an easy way to get a cert right now as an individual. A "real" cert is around $20-30 from top companies, and maybe $5-10 for others. Obviously someone could do their own for free.