3 ms·
OK done: we move to self signed certs. - Someone connects to wifi. - The wifi gives a DNS server. - The DNS server says some IP is foo.com. - foo.com isn't
by nailer 10y ago
OK done: we move to self signed certs.
- Someone connects to wifi.
- The wifi gives a DNS server.
- The DNS server says some IP is foo.com.
- foo.com isn't actually the foo.com you expect [1], but it's got a self signed DV cert so you connect to it, and give some bad person your data.
That's why we don't more to self signed certs.
[1] Of course, if you want to assert foo.com is actually the 'Foo, Inc' you were expecting that's a job for EV.
Disclosure: I made https://certsimple.com https://certsimple.com that focuses on simplifying the identity verification process for EV certs.
- foepys 10y agoTLSA DNS records coupled with DNSSEC could eliminate the need for CAs but we still have a long way to go until we can rely on it.
- hsivonen 10y agoDNSSEC has a 1024-bit RSA root after Web PKI ( at least Mozilla-flavored) no longer did. Are the TLDs audited like CAs? Having to change the domain name to evade the TLDs bad security practices is more disruptive than switching CAs.
- mastax 10y agoThen you just move all the WoT issues of the CA system into DNS, no?
- foepys 10y agoYes. But you could argue that securing DNS is necessary anyways and using it for TLS is just the next step.