3 ms·
> CA can expect that its connection to your DNS server is reliable and not tampered Why? It goes over infrastructure that you nor they control. It might be wo
by lucb1e 8y ago
> CA can expect that its connection to your DNS server is reliable and not tampered
Why? It goes over infrastructure that you nor they control.
It might be worth illustrating what happens here, as it's not immediately clear from common DNS settings or common commands. First, the client asks their local DNS server, the one you get via DHCP or configure (for example 8.8.8.8 which is by definition already outside your network, but for argument's sake let's assume that they're smarter than that and they pick one inside their own network). Let's say this one doesn't have it in cache, so then it has to go out and ask the TLD (let's assume it has the TLD cached).
The TLD, for example `.com`, will say "the name servers for your.example.com can be found at ns.your.example.com" and it gives the IP addresses for those. Now the local resolver at the CA has to go and ask there for your domain. In this final step, if nowhere else, it will have to leave any sort of trusted network and venture into whatever place the user's servers are at. This could be anywhere in the world, with all sorts of intermediate networks.
- geocar 8y ago> Why? It goes over infrastructure that you nor they control. They're able to use many secret locations to perform the query. There is a theory that it is very unlikely an attacker can detect and get leverage over every network between every one of those secret locations for an indeterminate amount of time, without being discovered.
- jessaustin 8y agoWhat you describe is a possible technique that CAs could use, so let's stipulate that some CA does this. We certainly can't conclude that all or even many CAs do this.
- cormacrelf 8y agoI’m pretty sure AWS Certificate Manager does this.
- vbezhenar 8y agoAttacking server infrastructure is order of magnitude harder than attacking user. Those who can do this attack, can just ask their CEO to issue them a certificate via subpoena.
- tialaramex 8y agoOne very simple reason is that they tell their service provider that "No" they don't want the brilliant new anti-whatever service it's offering by tampering with DNS queries. Alas "No" isn't an option for that public WiFi access point you're using, or most mobile service, or your mom's Internet, the average corporate workplace, and so on. So even though this is hardly foolproof it makes a huge difference.