3 ms·
The actual DNS server still needs to implement DNSSEC, the registrar won't do that by themselves. Still, as an end user, I don't care who implements it, all I k
by jeroenhd 6y ago
The actual DNS server still needs to implement DNSSEC, the registrar won't do that by themselves. Still, as an end user, I don't care who implements it, all I know is that the records I received are intact and have not been tampered with by any intermediary parties. This makes it a lot easier to trust my DNS provider.
Yes, DNS becomes a CA in schemes such as DANE, but a CA that the domain administrator controls. I don't see any problem with that. We've been spoiled by Let's Encrypt by now, but free, easy TLS certificates and management for even small businesses are a very recent thing.
I much prefer the decentralised nature of DANE over current CAs, even from parties like Let's Encrypt. LE is still an American company and the USA has been proven to be all but transparent and friendly to its allies when it comes to using their power over digital infrastructure for their gains. I am 100% sure that if LE receives a red security letter instructing them to generate a certificate for a certain domain, they will, just like any CA would, before that CA would collapse as soon as anyone finds out. My bank's website security depends on nobody on the other side of the Atlantic getting any funky ideas.
The decentralised nature of DANE makes it a nice system because worst case scenario, some TLDs do not get signatures during the next key rollover. This would be immediately obvious to any observer, so actions like these cannot be done in secret.
- tptacek 6y agoThe problem isn't simply that the DNS becomes a CA. It's that it can't replace existing CAs --- the browser still has to support the WebPKI. So what you have in effect is another CA, a 1001th, if you will, and one that the browsers can't revoke.