5 ms·
Certificate Authority Authorization (CAA) Research Study
- deleted 9y ago[deleted]
- Shoothe 9y agoLast time I checked Cloudflare had incomplete support for CAA (no issuewild or flags). OHV also mentioned they are working on it but that was half a year ago and so nothing.
- regecks 9y agoThey definitely support issuewild now, but annoyingly will inject their own extremely broad CAA records into your zone unless you go into a different UI and hit "Disable Universal SSL" down the bottom of the page, even if you don't use their proxy service. I tried submitting feedback about this but I assume it got ignored by the support rep. Not a huge fan of the CAA UI. I would prefer the option to enter the RRs in a raw format (like TXT records), even if it's not the default UI.
- Shoothe 9y agoThat they generate certificates with my name was such a bewildering move (I knew as I monitor CT logs). I had to contact support for them to stop as they admitted there was no UI for that. > Not a huge fan of the CAA UI. I would prefer the option to enter the RRs in a raw format (like TXT records), even if it's not the default UI. Couldn't agree more. No SSHFP too. I'm waiting for OVH to add CAA records and I migrate back to them.
- Avamander 9y agoI sent a support request a few weeks ago asking for CAA recently too, they didn't even indicate they were planning to add that.
- aplorbust 9y agoWhomever controls DNS controls Web PKI. True or false? Please explain your answer. You may assume "controls DNS" means potential control over delivery or content of unencrypted DNS packets, e.g. the operator of a parent nameserver, the operator of an open resolver, a delegated authoritative nameserver (e.g., Cloudflare), someone else intercepting and modifying packets, etc. Rephrased question: In what ways, if any, is Web PKI dependent on DNS?
- regecks 9y agoDNS, or whois (43/tcp), or the ability to retrieve/fabricate government documents. There are plenty of documented ways that the Web PKI can be subverted.
- bluejekyll 9y ago> control over delivery or content of unencrypted DNS packets And thus we are back to asking for DNSSec. With DNSSec all Records are signed with RRSIGs, and can be validated as being legitimate answers. Your client needs to support validating these of course. Now, there are a lot of people who don't like DNSSec, and I don't blame them. It's a hot mess in terms of deployment, etc. It feels like with CAA, TLSA, and other record types we're getting closer to some of the security people want in DNS. We also now have a pretty decent RFC for DNS over TLS, which provides privacy (where needed) in addition to the signed records. We should be able to come up with a solution to securing DNS by utilizing the existing CA systems out there. Where we could sign zones, and verify them, independent of the chain of DNSKEY to DS records all the way back to the root (this would be different from the current DNSSec validation). I'm not aware of any existing RFCs for something like this.
- aplorbust 9y ago"> control over delivery or content of unencrypted DNS packets And thus we are back to asking for DNSSec." DNSSEC does not encrypt DNS packets. (Nor does TLS encrypt UDP DNS packets per packet. It encrypts a TCP stream.) Not interested in a debate over DNSSEC, but please note I used the word "unencrypted" for a reason. Not only can the contents of unencrypted packets be tampered with, but, if I am not mistaken, djb has suggested DNSSEC signed RRs are still vulnerable to forgery.