Re:Telco lobbyists accidentally send their talking points
by mrkstu on Friday August 31, 2018 @06:38PM
(#17889029)
Well they do, in point of fact. I was debugging our corporate proxy and tailing the logs for a particular site- when using chrome I matched the site string despite it being directed to bypass proxy- but not going to the site, but to google, despite putting a full url in.
Anyone wanting to truly understand what chrome is doing should run an ssl decrypting proxy on their web traffic for awhile- it is eye opening.
Re:Telco lobbyists accidentally send their talking points
by jrockway on Monday September 03, 2018 @04:29PM
(#17904715)
Perhaps more interesting is that Chrome is happy to send data to google.com without checking the certificate. I'd file a bug.
Re:Telco lobbyists accidentally send their talking points
by mrkstu on Wednesday September 05, 2018 @10:54AM
(#17918515)
Yep, their not pinning that cert, but I think this is purposeful to continue to function in corporate environments like ours where we deploy our own Cert chain infrastructure. So the OS and transitively the browser is seeing a 'valid' certificate if you're browsing from a company computer.
Firefox on the other hand, you have to import the whole CA chain into the app itself for it to work transparently, since it won't reference the OS cert store.
I don't say they do, but my trust in Google not to do this isn't that much higher than ISP s not doing this.
(Though, to be fair, code doing this would probably be found rather quickly in the Chromium code. So they'd have to add it to the Chrome binary directly.)