Re:The unintended consequences of blocking IP addresses
by JamesonNetworks on Thursday December 29, 2022 @07:18PM
(#34179956)
Its unbelievable that they are taking control out of local sys admin hands rather than enabling them with better tooling. It puts packaged software in the same vein as Comcast and Spectrum hardware or Google WiFi that doesn’t expose router and dhcp settings. We are heading to a world where all software for personal use will need to be custom built to rip out all this user and admin hostile nonsense
[ Parent
| on HN ]
Re:The unintended consequences of blocking IP addresses
by josephcsible on Thursday December 29, 2022 @11:41PM
(#34181854)
> they are taking control out of local sys admin hands
How so? Do any programs force the use of DoH and don't let you configure which server they use?
Re:The unintended consequences of blocking IP addresses
by p_l on Friday December 30, 2022 @09:07AM
(#34185091)
Mozilla openly mentioned they might block network-wide methods to disable DoH and majority of people do not know that Mozilla (or Chrome etc.) are going to use their own settings, leading to unexpected behaviours.
Re:The unintended consequences of blocking IP addresses
by josephcsible on Friday December 30, 2022 @11:56AM
(#34186883)
> they might block network-wide methods
How is that taking control away from a local sysadmin? It'd be a great thing if they did that, since then malicious network administrators won't be able to disable DoH on computers that aren't theirs anymore. If you're really trying to control devices that are yours, you'll still be able to turn it off via local Firefox policy.
Re:The unintended consequences of blocking IP addresses
by p_l on Saturday December 31, 2022 @01:45PM
(#34199377)
There's a spectrum of options between "total lockdown of machines" and "nothing is controlled". Also, at least the way the announcement read at the time... it felt like someone forgot that there might be a need by local admin to disable it, in fact.