3 ms·
Unfortunately, Chrome's current policy is to disable certificate transparency and HPKP when a certificate appears to have been manually installed, to support MI
by michaelt 11y ago
Unfortunately, Chrome's current policy is to disable certificate transparency and HPKP when a certificate appears to have been manually installed, to support MITM proxies [1].
Needless to say, this makes HPKP and certificate transparency worthless when the client has been compromised by adware or viruses.
[1] https://www.chromium.org/Home/chromium-security/security-faq#TOC-How-does-key-pinning-interact-with-local-proxies-and-filters- https://www.chromium.org/Home/chromium-security/security-faq...
- kuschku 11y agoAnd then you set a Group Policy to ban Chrome and instead enable a browser with more reasonable settings for this case, like Firefox.
- lmm 11y agoWhat are Firefox's settings for that case then, hmm? Does Firefox refuse to work with MITM proxies at all?
- magicalist 11y agoFirefox accepts local certs over pinned ones by default as well (superfish affected it too). I believe there is an about:config setting that can be changed to have it reject local certificates in the face of a pinned site, but if malware is putting certificates in Firefox's cert store, they can just as easily flip that setting as well.
- Dylan16807 11y agoHint: they do this because of group policy adding certificates
- yrro 11y agoWhy don't they change the green lock icon to a blue icon indicating a pair of eyes, that when clicked on explains that the connection is not secure because your IT department is monitoring the connection?
- lucaspiller 11y ago> Chrome's current policy is to disable certificate transparency and HPKP when a certificate appears to have been manually installed, to support MITM proxies Sidenote: Is there a way to disable these on iOS to inspect SSL traffic through a MITM proxy?