News for hackers. Stuff that matters.
Re:The DNS-Based Authentication of Named Entities (DANE) TLS... by tptacek on Monday August 29, 2016 @01:29PM (#12383527)
First, nobody believes any part of the FVEY IC can't already get TLS certificates. DNS spoofing? They've already got CA=YES certificates.

Second, DNSSEC doesn't even prevent this attack! All it does is attempt to protect name lookups. SMTP itself doesn't magically become secure just because there was a signature on an A record.

Finally, we're already doing something that meaningfully blunts this attack. No matter how the CA system is compromised, browsers still monitor certificate pins. When pins break, the CA associated with the malicious certificate gets reported. When that happens, as we've seen repeatedly, the CA gets penalized --- or put out of business entirely.

Public key pinning, CT, and surveillance is actually making a dent in the Internet trust problem. DNSSEC is a charade --- or, I think, something worse than that: you can't simply "revoke" .COM.

Re:The DNS-Based Authentication of Named Entities (DANE) TLS... by 0x0 on Monday August 29, 2016 @01:49PM (#12383688)
Maybe we could

1. take away all the existing CA=YES certificates

2. stop using SMTP for domain verification, and issue the certificate at the same place that a domain's NS records are set (i.e. in a domain registrar's control panel), preferably in way that clients won't accept certificates issued by unrelated (and there unauthorized) domain registrars.

As I mentioned the other day, nobody is talking about revoking ".com". We'd have multiple registrars under ".com", and if one behaves badly, revoke that particular registrar. Also, if ".com" itself is out to spoof you, then you have already lost as a .com domain owner, so maybe we SHOULD revoke all of .com if proof of that surfaces, so that everyone will know that .com can't be trusted at all anymore.

Re:The DNS-Based Authentication of Named Entities (DANE) TLS... by tptacek on Monday August 29, 2016 @01:53PM (#12383724)
Maybe we could actually fix the problem instead of just moving it around.