News for hackers. Stuff that matters.
Re:Making email more secure with MTA-STS standard by hannob on Thursday April 11, 2019 @02:50AM (#19631760)
DNS is usually not secure. DNSSEC is not deployed widely. End of story.
Re:Making email more secure with MTA-STS standard by josteink on Thursday April 11, 2019 @05:40AM (#19632458)
All security of everything on the internet relies on DNS.

If the problem is that DNS isn’t secure, nothing is, and DNS should be fixed first instead of fucking up every other internet protocol instead with crappy bandaids. That’s just obvious engineering.

The people behind this spec are obviously incompetent or have ulterior motives.

Re:Making email more secure with MTA-STS standard by tptacek on Thursday April 11, 2019 @12:29PM (#19636290)
Virtually none of the security of the Internet depends on the security of the DNS; not depending on DNS for security has been an explicit design goal of Internet cryptography since the mid-1990s, which is, for instance, why IPSEC and DNSSEC evolved separately (DNSSEC was a DoD project spearheaded by TIS).
Re:Making email more secure with MTA-STS standard by zeroimpl on Thursday April 11, 2019 @09:58AM (#19634567)
Yes, I don't see how this MTA-STS avoids the DNS security issue. The system first uses a DNS TXT record to indicate a policy exists, then uses HTTPS to fetch that policy.
Re:Making email more secure with MTA-STS standard by dcbadacd on Thursday April 11, 2019 @10:30AM (#19634872)
We have a standard for protecting DNS, but it's so bad - the tools are bad, the % of deployment is bad, the resolvers handle it bad, the ability for a regular sysadmin to deploy it is bad, it's just super bad compared to what we have with the HTTP PKI.