71–80 of 673 posts
Earlier quoted context omitted.
Just don’t ever connect it to your network.
How do you do this? Wrapping it in grounded tin foil? Ripping out the wifi module? Do I need to void warranty and dissect a new piece of consumer electronics to remove the spy organ? Is that really an acceptable situation?
Earlier quoted context omitted.
How do you do this? Wrapping it in grounded tin foil? Ripping out the wifi module? Do I need to void warranty and dissect a new piece of consumer electronics to remove the spy organ? Is that really an acceptable situation?
Put a password on your wifi, it other security benefits as well.
Earlier quoted context omitted.
The root evil here is that you can't change the root certificates in such devices. Even if you controlled its DNS, the device could still just be programmed to fail if it doesn't reach its analytics/ad/whatever server.
The Amazon Fire TV does this already :( If it doesn't see internet it just blocks itself and goes to a screen "Oops I have no internet". So you can forget about watching movies from your local server using the VLC app as well. Ridiculous.
Earlier quoted context omitted.
It’s a gamble, not a guarantee. What happens when your hard coded DNS is not available? The more convincing narrative is that setting custom DNS decreases ad revenue and cuts into growth.
>What happens when your hard coded DNS is not available? The same thing that happened each time when DRM servers went offline. Time to buy a new TV :^)
Earlier quoted context omitted.
How do you deal with NAT64? It's a real thing with some consumer ISPs. I can see myself using it as well, maybe even just to see which devices don't use DNS. Here's another idea: generate a unique IPv6 address per DNS request, route them to the correct destination, filter other IPs. Not really scalable, but usable on small networks/VLANs.
Currently, we don’t. The devices don’t support IPv6, so it’s not a problem we’ve had to deal with so far.
I’m responsible for a bunch of IoT hardware, and every firmware spec I write includes a note on not using the DNS servers provided via DHCP. While sure there are companies explicitly doing this to avoid filtering, at least in my case it’s because a significant proportion of DHCP servers are configured to send DNS to your ISP, and ISP provided DNS is almost universally terrible. They’ll ignore TTLs, rewrite NXDOMAIN r…
> and ISP provided DNS is almost universally terrible. They’ll ignore TTLs, rewrite NXDOMAIN responses into the IP address of their ad-laced web search, and occasionally just highjack every single query to send you to a page saying you’re approaching your bandwidth quota Universally? Perhaps in the US? But IoT devices are sold worldwide. While I do run my own recursive resolver I checked my ISP's and they're behaving…
Before going with the conspiratorial take note that Mozilla shipped DoH early and both Microsoft and Apple implemented it. Untrustworthy ISPs are a real problem even if Google deservedly gets suspicion about their motives. This isn’t another AMP.
Earlier quoted context omitted.
Just don’t ever connect it to your network.
How do you do this? Wrapping it in grounded tin foil? Ripping out the wifi module? Do I need to void warranty and dissect a new piece of consumer electronics to remove the spy organ? Is that really an acceptable situation?
Earlier quoted context omitted.
How do you do this? Wrapping it in grounded tin foil? Ripping out the wifi module? Do I need to void warranty and dissect a new piece of consumer electronics to remove the spy organ? Is that really an acceptable situation?
Does your TV magically crack the WPA2 password?