3 ms·
> There's no real way to "patch" this. Just disable custom DNS. Only allow a few whitelisted DNS that 99.9% of people are going to use anyway.
by backpropaganda 8y ago
> There's no real way to "patch" this.
Just disable custom DNS. Only allow a few whitelisted DNS that 99.9% of people are going to use anyway.
- detaro 8y agoWhat does that gain? It prevents people from browsing the web, what's the issue with that? For exploits/jailbreaks/... it'd be easy to use a local fake captive portal, so it doesn't protect against that unless they kill that feature completely, making the device unuseable with many networks.
- voltagex_ 8y agoIt would also prevent people with jailbroken devices from blocking *.nintendo.com so there's that.
- krageon 8y agoIf you own the network it's not super hard to just filter all traffic doing DNS. If you have a properly owned phone, you can probably run this over your phone hotspot and do the packet inspection that way. Then you can block all nintendo traffic, while still not having a "custom" DNS. If you really tried, you could still even have your custom DNS except it would be spoofing another server. The point is that if you own the network (and you do), then the clients are nominally at your mercy.
- IntelMiner 8y agoHow do you define "custom" DNS exactly?