If they truly did nothing, that would probably be better.
What they actually do is turn the setting off where most people test it to check that it is doing what it claims, i.e. running a WWW browser or suchlike application interactively, whilst covertly leaving it on in non-interactive but pretty serious parts of the system.
Until one day you fiddle with the #ProxyAutoConfiguration file, thinking that it's not in use, and you find that your supposedly dummy HTTP server is getting a lot of requests.
JdeBP (@[email protected])
I've run ktrace/truss on the HTTP server as the easiest way to find out what requests it was receiving, given that they're either being conveniently downgraded from HTTPS to a CONNECT over HTTP, or were in HTTP already. There is good news and there is bad news. The good news is that there's nothing particularly new amongst the URLs. Microsoft discloses a lot, but not all, of them. A couple belong to other companies, but the connections to Microsoft, Google, et al. are overt. The bad news is that these are things like certificate revocation lists from Google, other certificate information, your Microsoft account login on Windows Live, Bing Maps, Windows Defender updates, and various other stuff. And they're all vulnerable to a WPAD attack on an untrusted LAN (e.g. your favourite Internet café) that has been known about for over 20 years. And, importantly, that the system administrator *thinks is turned off*. #MicrosoftWindows #WPAD #ProxyAutoConfiguration #infosec