4 ms·
> DNSSEC is a hierarchical PKI, like the CA system. Just off the root of the DNSSEC hierarchical PKI are a series of branches that are controlled entirely by wo
by danyork 12y ago
> DNSSEC is a hierarchical PKI, like the CA system. Just off the root of the DNSSEC hierarchical PKI are a series of branches that are controlled entirely by world governments.
I am assuming you are talking about the country-code TLDs (ccTLDs) here, correct?
I agree that certainly many of those ccTLDs are directly controlled by governments while many others are operated on behalf of governments.
The generic TLDs (gTLDs) are different and are mostly operated by private companies operating registries under contact with ICANN. With the "new gTLD" program there are now MORE gTLDs than there are ccTLDs.
> I don't know how to say this any more clearly without sounding patronizing. In a DNSSEC/DANE world, the Libyan government can successfully publish a fake certificate for BIT.LY.
Simple answer - if you don't trust the Libyan gov't, don't use a .LY domain! I would argue that in DNS in general you do need to trust your parent zone. If you don't trust them, don't use them. Period.
- rakoo 12y agoIf you are a service provider, then yes, you can avoid using any TLD. If you're a user, you can't use bit.ly services with DNSSEC without trusting the .ly TLD, right ?
- danyork 12y ago> If you're a user, you can't use bit.ly services with DNSSEC without trusting the .ly TLD, right ? True, although you can remove the "with DNSSEC" part. You can't use bit.ly (or any other .ly) without trusting the .ly TLD. Interesting, I wasn't thinking about it from the user point of view - I was thinking about it from the domain registrant who is publishing a DNS zone under .LY. But you're right that it equally applies to the end user from the client perspective.