Re:The unintended consequences of blocking IP addresses
by josephcsible on Friday December 30, 2022 @01:50PM
(#34188435)
If it's possible for you to do what you're describing to your own IoT device, wouldn't it also be possible for you to do it to other people's laptops and phones that are on your Wi-Fi?
Re:The unintended consequences of blocking IP addresses
by kortilla on Friday December 30, 2022 @05:09PM
(#34190670)
Might be, but that’s not my concern as an operator of my private home network.
It’s completely fine for there to be conflicting goals even held by me. I want to not have my traffic interfered with when I’m on someone else’s network but I don’t want the vulnerable internet of shit stuff to be even more opaque on my network.
Anyway, the fourth category is people who want to own their devices on their network and are being fought by the vendors of their Internet of things devices. When I have dns queries I can build a pattern of what it takes some rando device to operate and then lock down and alert on anything else. Can’t do that with DoH.
With DoH, I just have to allow opaque DNS smuggling to the wider Internet and hope that the device hasn’t been compromised. It’s trivial to run bidirectional c&c over DNS and DoH makes that invisible to anyone. It’s a monumental step back in security for the local network to improve the privacy of the individual device.