Re: [pfSense] Problem with Chrome - HTTP trasnparent proxy with SSL filtering

Public or private CA, the issue will persist. On Nov 3, 2017 8:39 AM, "Roberto Carna" wrote: > OK Jon, thanks for your time and explanation. > > So a last qustion please: now I put in Squid of pfSense a private CA > certificate...is it the same if I put a public CA

Re: [pfSense] Problem with Chrome - HTTP trasnparent proxy with SSL filtering

Chrome has a Certificate Pinninng feature. This feature takes the Google certs and checks their finger prints against the good known. AFAIK this is an issue with all HTTPS proxies from at least BlueCoat, Cisco, SonicWall and Checkpoint. The suggested solution is to bypass SSL filtering those