Re:New attack that cripples HTTPS crypto works on Macs, Wind...
by kuschku on Tuesday July 26, 2016 @02:43PM
(#12167869)
NetworkManager and dhcpcd will usually auto-configure with WPAD, and all major browsers will use it.
If you're using KDE, you can disable it under
System Settings > Network > Settings > Proxy > No Proxy.
If you want to disable it for the browsers, see https://news.ycombinator.com/item?id=12167767
Re:New attack that cripples HTTPS crypto works on Macs, Wind...
by daveloyall on Tuesday July 26, 2016 @03:19PM
(#12168104)
I don't use network manager. I do use wicd. Looks like I have isc-dhcp-client, not dhcpcd5.
The DNS-based mechanism might get me, though... I don't know. Is that implemented exclusively at the browser layer?
Re:New attack that cripples HTTPS crypto works on Macs, Wind...
by eikenberry on Tuesday July 26, 2016 @10:58PM
(#12170207)
I don't think dhcpcd5 does this. Do you have a reference?
Re:New attack that cripples HTTPS crypto works on Macs, Wind...
by eikenberry on Tuesday July 26, 2016 @11:01PM
(#12170214)
Found the reference.. it supports wpad when used as a dhcp server. It doesn't support it as a client.
BUT... I was unaware of this DHCP attack surface for WPAD. Does anybody know if Debian has some scripts for receiving a URL via that mechanism and then visiting it? I guess this would be achieved by libproxy or something?
Do the browsers do some WPAD stuff independently?