Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default
by zzzcpan on Saturday September 07, 2019 @02:36PM
(#20905652)
Network administrators don't have power over device administrators, so the premise is a bit false. Device administrators are the network administrators on their own devices.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default
by throw0101a on Sunday September 08, 2019 @09:35AM
(#20910482)
> Network administrators don't have power over device administrators ...
They (possibly) do when they're both under the same Director of IT.
Security is everyone's responsibility in an organization, and the folks in Helpdesk (ideally) want to prevent intrusions just as much as the NetOps folks.
The status quo implementation has been that the operating system handled DNS, which actually did put the power in the hands of the device administrator: I don't think I have ever seen a device that wasn't clearly owned under some crazy MDM scheme where you couldn't choose your own DNS servers. Sure: recently, it happened to have a default to trust the network... but that was just a convenience, and is a "new phenomenon" brought on by DHCP being widely deployed. All of the software wasn't designed with that as an assumption.
So, if I want DoH, why am I not just setting up a custom resolver on my computer, that all of my apps use, including Firefox? The "power struggle" alluded to up-thread is actually much deeper: it is using network operators as an excuse to take power away from users, by moving what used to be an operating system feature into individual applications in a world where DRM via code signature is being deployed to lock users into curated application domains to prevent them from modifying that software to do what they want.
(That said, I mean... the way Firefox implemented this totally still gives the network administrator control, due to the opt-out provision? So in some sense a lot of this conversation is useless... for now.)