4 ms·
I think you've misunderstood what whyleyc wrote above. OP asked why GoGo doesn't just "blacklist" ie censor the mentioned sites via DNS, explicitly excluding a
by Panino 12y ago
I think you've misunderstood what whyleyc wrote above. OP asked why GoGo doesn't just "blacklist" ie censor the mentioned sites via DNS, explicitly excluding a MITM attack:
> Why are they even pulling this MITM trick in the first place ?
> Can't GoGo just "blacklist" streaming sites at a DNS level and deal with the problem before a connection is even made to a high-bandwith destination ?
So no MITM, just GFW of China style blocking. Which is trivial for unencrypted packets like DNSSEC. Observe, by the way, that China supports DNSSEC -- it's not a problem for them!
http://dnsviz.net/d/cn/dnssec/ http://dnsviz.net/d/cn/dnssec/
And it wouldn't be a problem for GoGo, either, because DNSSEC is not encrypted and blacklisted sites can be dropped on the floor. Or GoGo could trivially return SERVFAIL. But the whole thing is moot anyway because youtube.com doesn't support DNSSEC and probably never will.
- wtallis 12y agoBlocking DNSCrypt entirely and forcing a fallback to the approved (censored) DNS servers is still not any harder to accomplish than censoring unencrypted DNS with or without DNSSEC. DNSCrypt as it currently exists is not any more censorship-resistant except where it is completely unknown to the censoring party. The only real security (against censorship) that it offers is security through obscurity, so saying that DNSSEC's problem is a lack of encryption is complete bullshit.