4 ms·
What depresses me is that many organisations agree that SMTP needs some work. However the stakeholders simply don't care enough to do anything about it, all Goo
by Someone1234 11y ago
What depresses me is that many organisations agree that SMTP needs some work. However the stakeholders simply don't care enough to do anything about it, all Google is doing here is adding a pretty little icon for opportunistic encryption (that doesn't work very well).
Let's look at the biggest stakeholders in SMTP:
- Microsoft: Exchange (8% mail servers), Outlook (client), Outlook.com (23% of webmail).
- Google: Gmail & Google Apps (40% of webmail)
- Yahoo (21% of webmail)
- OSS: Sendmail, Postfix
So if Google, Microsoft, and Yahoo! signed up that is the majority of SMTP on the internet today. Then we find some funds to get OSS updated (or summer of code), and boom, we have an SMTP update fit for 2015.
Heck have it downgrade for right now, and we can talk about actually switching over in 2025 or whatever. But at least in 2025 we'll have something ready, the longer we take to kick this off the longer it will take to upgrade.
It is utterly insane that nothing is moving here. It is like SMTP is stuck in a perpetual IE 6 situation, and Microsoft is largely causing it all over again (Exchange + Outlook.com).
- yid 11y ago> However the stakeholders simply don't care enough to do anything about it, Perhaps that's a sign that "it" (smtp) now works well enough with the decades of engineering investment put into spam detection, access, standardization and inter-operability that have been put into it to not justify the massive investment that an "SMTP update fit for 2015" would involve.
- mschuster91 11y ago> spam detection, access, standardization and inter-operability Spam detection works on a higher level than transport security, it is independent from transport (although a spam classifier might favor mails from SMTP servers sent with SSL and a client certificate signed by a CA for its domain name). Access... well, that's IMAP/POP3's job, both support SSL for ages. Standardization/interop, uh we already have SMTPS. The standard is there, what's lacking is support for inter-server encryption.
- darkr 11y agoSMTPS has been deprecated since forever (late 90's or thereabouts). The standards for encrypted SMTP are: STARTTLS over port 25 for transfer/relay and STARTTLS over port 587 for submission.
- feld 11y agoBut STARTTLS is a step backwards because a MITM can disable crypto by not advertising STARTTLS
- 0x0 11y agoA MITM could also deny SMTPS ports. If you want to ensure STARTTLS is in use then most smtp software has a setting to force STARTTLS or drop the connection.
- lox 11y agoMy understanding that the issue is that attackers will then just do STARTTLS with their own self-signed certificate, as checking the common name of the certificate is difficult in the context of SMTP.
- mschuster91 11y agoWell, use DNSSEC and add a new field in the DNS (e.g. CRYPTINFO = FORCE-HTTPS, FORCE-SMTPS). That would take time to spread, yes, but it would be a perfect solution for a lot of "prevent MITM downgrade" issues.
- feld 11y agoYes, it would take a long time to spread considering there's a whopping 388 domains out there using DNSSSEC for SMTP, the majority of them run by neckbeards and not commerical email services. 388 Zones have deployed TLSA for SMTP with STARTTLS (Port 587) I don't expect this to catch on, ever. http://secspider.verisignlabs.com/stats.html http://secspider.verisignlabs.com/stats.html
- rob-olmos 11y agoGoogle's Online Security Blog posted earlier today regarding improving email security including "opportunistic TLS"[1] through the M3AAWG association, which does list the above companies as either sponsors or members[2] 1: https://googleonlinesecurity.blogspot.com/2015/11/new-research-encouraging-trends-and.html https://googleonlinesecurity.blogspot.com/2015/11/new-resear... 2: https://www.m3aawg.org/about/roster https://www.m3aawg.org/about/roster
- baudehlo 11y agoThis unfortunately shows you know little about the forward momentum in the email standards. There have been many changes in the last few years that you just didn't see. DMARC creates policies on authentication. DANE creates policies on SMTP encryption. These technologies are gaining wide implementation and acceptance. MAAWG meets three times a year to move these things forwards. Just because the standard dialog here is "SMTP sucks, let's replace it" doesn't make it true. People are working harder than you think on solving these problems.
- fulafel 11y agoSMTP is hop by hop, so it's the wrong layer for addressing privacy. Starttls only happened because it was zero effort to turn on and gets you possibly little opportunistic privacy.