3 ms·
A corp network should set up their own DoH resolver anyway. And/or simply install a cert on their workstations and MITM every TLS connection. Even better corps
by pas 8y ago
A corp network should set up their own DoH resolver anyway. And/or simply install a cert on their workstations and MITM every TLS connection.
Even better corps should only allow TLS that they can successfully MITM.
It's basic security. If the endpoint/host can do whatever due to lack of firewall/enforcement, then it doesn't really matter what the network operator wants.
- deleted 8y ago[deleted]
- cremp 8y ago> A corp network should set up their own DoH resolver anyway What good is that is the browser uses their own list? Literally that's what the article is saying. Firefox will force users to use ones that break the top-down approach on how software works. If I set a DHCP option for DoH, and setup my own DoH resolver, Firefox wont care, they will jsut use their list. This also opens up possibilities for selling positions on the trusted list, because we've seen that happen before (adblock, or the firefox Mr Robot extension.) Firefox itself, with plays like this are trying to make a decision about the whole, when they are completely forgetting the corporate side.
- wbl 8y agoYou can still administer the machine and change firefox's settings.
- vetinari 8y agoMost people roam among multiple networks. Are you going to change the settings manually after each connection in different network? Most people won't. We already have an automation for that, called DHCP, setting up network specific config system-wide... which Mozilla decided to ignore.
- wbl 8y agoSo whose device is it anyway? I don't want to use my ISP's lying DNS resolver.
- vetinari 8y agoOn your router, you can configure whatever you want to use for the DNS. You were able to do that for years. But I want all the devices and apps to use whatever the local network tells them. I don't want to reconfigure the browser every time I connect at home/work/customer place/etc. P.S. My ISP's DNS doesn't lie. Maybe you should vote with your money and choose better.
- Spivak 8y ago"Network operators should be able to set DNS servers for client devices." "You can configure your router, a client device, to use whatever DNS server you want in defiance of your ISP, a network operator." Which one do you want?
- vetinari 8y agoIf you configure your router, you are the network operator (of the network that the router handles). Mozilla or other app vendors are not. No dichotomy there.
- Spivak 8y agoThe point is that your router is a client of your ISPs network and you're overriding the servers provided by DHCP to your router. In a crazy world where internally Firefox ran a small IP network for each tab and routed traffic between them for IPC would it suddenly be okay for Firefox to override DNS? Why or why not?
- vetinari 8y agoThe difference is not in what is being done, but in who is in charge. If you modify your router settings, it's you. You decided that you are not going to honor ISP suggested defaults, and it is up to you to assess costs/benefits and pick the right choice. If Firefox overrides your settings, it means someone else does the decision about your tools. If that someone else makes it difficult to automate changing the default (e.g. ignoring DHCP; if you want, you can ignore DHCP at the system level, but this is not a decision an app should take), it means, that this someone else doesn't have good intentions towards you. Someone else decided what's "best" for you.
- raxxorrax 8y agoI am no sysadmin but working closely with some. I have never seen any case where HTTPS-MITM helps. Yes, theoretically it does allow us to scan for malicious content in a secured connection. Brilliant, but that are not the attack vectors they are concerned about. So what is left is that breaking up TLS just infringes on privacy and allows for tighter control. The security aspect is laughable. Users are angry that their internet got slower, an it creates an enormous administrative cost, because you need countless exceptions to the rules. Most developers break out of it in a few days...
- dogecoinbase 8y agoI am no sysadmin but working closely with some. Some of your best friends, eh? The point of MITMing HTTPS in an enterprise setting is not inbound content scanning (though that's pretty useful to), it's to prevent outbound transfer of secrets/HIPAA or PII data/financial data, and it's a regulatory requirement for some industries. Besides, the point of DoH is to move DNS into the browser, which Google also controls, to prevent pihole-like DNS-based ad blocking. Cloudflare supports it because it allows them to lock down one of the few remaining actual distributed systems powering the internet. These companies are not your friends, and you should think harder about their incentives.
- Spivak 8y ago> it's a regulatory requirement for some industries. It won't be when it's functionally impossible, which seems to be the point. You do see the light at the end of the tunnel, right? Browsers shipping their own unmodifiable CA stores and disrespecting 3rd-party CAs signatures for public DNS names.
- pas 8y agoIt seems you don't understand that there's Firefox ESR and other browsers too. The law very likely won't change just because consumer-friendly browsers by default are not enterprise-friendly. Big corps provision and manage their machines themselves, they modify the packages' built in configuration (they either create a new install package, or do it after install with scripts, or - if the application supports some kind of "group policy" then they use that). Cost of compliance is a real thing, and making the workstations secure and compliant with their own policy is their responsibility in those industries. It's not fun, but it's perfectly doable.