Re:CAA checking becomes mandatory for SSL/TLS certificates
by tialaramex on Wednesday April 12, 2017 @09:29AM
(#14097448)
There is at least one CA that simply doesn't offer DV. So if you happen to agree with them that DV is worthless (for the record I do not), or at least that it's never appropriate for your business, then setting CAA to require that CA means nobody will be using some scheme to get "legitimate" DV certificates for your domain.
Re:CAA checking becomes mandatory for SSL/TLS certificates
by jpalomaki on Monday April 10, 2017 @10:50AM
(#14078924)
The standard also makes it possible to add CA specific limitations. The RFC shows as example how you could setup the record do that CA will only serve requests for specific customer account.
Since there's quite much competition on the field, I would assume CAs will be eager to implement these kind of value add services.
I don't see how CAA protects against this. If you're using CAA, presumably your email admin could just request a certificate from one of the whitelisted CAs. The only saving factor is if your whitelisted CAs don't support email-based verification.