Re:CAA checking becomes mandatory for SSL/TLS certificates
by michaelt on Monday April 10, 2017 @08:57AM
(#14078078)
A third party can validate CAs to ensure compliance.
Domain owners can remove or change the CAA record after the certificate has been issued - so any third parties performing checking will have to be quick about it :)
Re:CAA checking becomes mandatory for SSL/TLS certificates
by okket on Monday April 10, 2017 @09:07AM
(#14078156)
Why would they? The idea of CAA is to help the domain owner, to prevent malicious issued certificates, to have a documented, open, visible way do identify which CA is authorised to issue a certificate. So, if you doubt what you see is legitimate, you have a way to check (also, when combined with DNSSEC, it is quite hard to forge/spoof).
Even without DNSSEC, every little bit of additional validation counts IMHO. You could e.g. trace sudden changes in CAA records and get very suspicious...
Re:CAA checking becomes mandatory for SSL/TLS certificates
by tptacek on Monday April 10, 2017 @12:42PM
(#14080038)
It's quite hard to forge or spoof to anyone except:
* The world governments that control the TLDs and can thus override DNSSEC policy by fiat.
* Any attacker between the CA's resolver and the DNS server, since DNSSEC only protects transations between DNS servers, not between clients and servers.
Plus combining this with Certificate Transparency should allow for handling this in an automated fashion. A third party can validate CAs to ensure compliance.