Re:SMTP protocol basics from scratch in Go: receiving email ...
by LeonM on Sunday April 10, 2022 @05:29AM
(#30975590)
> with a HSTS-like directive hosted in DNS.
I think you are talking about MTA-STS (rfc8461) [0]. It is currently being adopted by the larger email services (Google, Microsoft).
MTA-STS is not 'hosted' in DNS, but published via a policy service over HTTPS, so it uses PKI.
I work for Mailhardener, we offer MTA-STS policy services as a service [1]. We've seen an increased interest of MTA-STS recently, likely due to Microsoft announcing MTA-STS support [2].
[0] https://datatracker.ietf.org/doc/html/rfc8461 [1] https://www.mailhardener.com/blog/introducing-hosted-mta-sts [2] https://techcommunity.microsoft.com/t5/exchange-team-blog/in...
Re:SMTP protocol basics from scratch in Go: receiving email ...
by jeffbee on Saturday April 09, 2022 @11:51PM
(#30974346)
Yeah STARTTLS is fundamentally flawed that way. That's why Google and other SMTP interchange services allow paying customers (Google Workspace) to specify policy around TLS compliance.
Re:SMTP protocol basics from scratch in Go: receiving email ...
by 0x0 on Sunday April 10, 2022 @04:33AM
(#30975351)
I wouldn't say STARTTLS is fundamentally flawed. Given a mechanism for declaring a policy of TLS being required, a middlebox downgrade attempt to deny STARTTLS should merely cause the sender to abort the SMTP transaction. This is no different from a middlebox hijacking a pure TLS tcp connection. In both cases it's on the sender to abort if a secure connection cannot be established.
Re:SMTP protocol basics from scratch in Go: receiving email ...
by hsbauauvhabzb on Sunday April 10, 2022 @04:46AM
(#30975407)
Do real world smtp clients and servers do this? HSTS solves sslstrip type attacks, but I don’t think mail gets the same scrutiny..
Re:SMTP protocol basics from scratch in Go: receiving email ...
by Symbiote on Sunday April 10, 2022 @07:21AM
(#30976123)
A couple of years ago, someone with a .gov address told me they couldn't subscribe to a mailing list I manage, since the mail server didn't support TLS.
Adding the appropriate option in Postfix fixed the problem, and I think there were further options to require TLS.
Re:SMTP protocol basics from scratch in Go: receiving email ...
by sethammons on Sunday April 10, 2022 @08:38AM
(#30976467)
The initial call to starttls is already insecure. The server can say what it wants. We trust that it behaves.
Re:SMTP protocol basics from scratch in Go: receiving email ...
by 0x0 on Sunday April 10, 2022 @11:11AM
(#30977697)
I wouldn't consider the initial call to starttls to be insecure. It is just a matter of a few static bytes containing an SMTP HELO and the ascii bytes "STARTTLS". This can be used to establish a secure TLS connection without compromising any private information. It is only insecure if the client decides to proceed with the rest of the SMTP transaction if the server (or middlebox) nak's the STARTTLS. Which is no different from a middlebox presenting a self-signed TLS certificate. A few extra plaintext bytes at the start of the TCP connection containing the string "STARTTLS" doesn't change anything compared to a plain TLS socket. It is always up to the client to decide if it wants to proceed in the face of bad or nonexisting TLS.
Re:SMTP protocol basics from scratch in Go: receiving email ...
by hsbauauvhabzb on Sunday April 10, 2022 @01:14AM
(#30974639)
Interesting, any insight as to whether o365, and popular non saas servers do similar?
Re:SMTP protocol basics from scratch in Go: receiving email ...
by cube00 on Sunday April 10, 2022 @05:05AM
(#30975493)
SMTPS has been re-approved for use on port 465. The back story about this "wart" is documented in https://www.rfc-editor.org/rfc/rfc8314#section-7.3
Does the latter actually happen? Do smtp clients actively check this? What’s to stop some middleware performing a tls downgrade?