6 ms·
Need to go now, but here is my another $0.02 on this: yes, complex enterprise networks really benefited from WPAD (at least for some time) yes, it is primaril
by justsomehnguy 4y ago
Need to go now, but here is my another $0.02 on this:
yes, complex enterprise networks really benefited from WPAD (at least for some time)
yes, it is primarily Windows because... well, because it was implemented there
and yes, it's not used in *nix-like because for 99% of time any of them are not in the AD and doesn't support NLTM SSO, so on any Windows machine you get a seamless and silent auth on proxy, while any *nix-like at best nagged you for credentials with an explicit modal. Oh, you restarted your browser? Who are you? Can you provide your credentials?
> if the company stuff is set up right, there's nothing any of those URLs could grab. Or better, tack on some always-on VPN or whatnot when not on the trusted network and all the better.
yes, just like in any other case, a proper planning (preferably done before deployment) is a key for a proper security, by not having an attack surface in the first place.
- c0nsumer 4y agoKerberos, actually, not NTLM. And it is used in macOS (a *nix-like) and works great, either via WPAD (DNS), directly configured PAC file, or directly configured proxy server. It's Linux end user devices, specifically Ubuntu, that gives us headaches, mostly because there just isn't a system-wide HTTP library that handles it all which apps can depend on. So yeah, the prompting you describe is exactly the problem. (Not that macOS doesn't have it's own proxy problems... Configured on a per adapter/service basis only? With no easy way to get new NICs a proxy setting via some sort of system-default template? WTF?)