Re: [squid-users] SSL-bump certificate issues (mostly on Chrome, when accessing Google websites)

2015-02-06 Thread Amos Jeffries
On 6/02/2015 6:10 p.m., Luis Miguel Silva wrote: Dear all, I recently compiled squid-3.4.9 with ssl-bump support and, although it is working for the most part, I'm having some issues accessing some websites. The behavior is REALLY weird so I'm going to try and describe it the best I can:

Re: [squid-users] SSL-bump certificate issues (mostly on Chrome, when accessing Google websites)

2015-02-06 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First. Where is you cache can found openssl public CA certs? To validate connection from cache to server Squid must see root authority CA's. I.e (from my configuration. Note: all google services bumped and works perfectly): https_port 3129

Re: [squid-users] SSL-bump certificate issues (mostly on Chrome, when accessing Google websites)

2015-02-06 Thread Amos Jeffries
On 6/02/2015 9:32 p.m., Amos Jeffries wrote: On 6/02/2015 6:10 p.m., Luis Miguel Silva wrote: Dear all, I recently compiled squid-3.4.9 with ssl-bump support and, although it is working for the most part, I'm having some issues accessing some websites. The behavior is REALLY weird so I'm

[squid-users] SSL-bump certificate issues (mostly on Chrome, when accessing Google websites)

2015-02-05 Thread Luis Miguel Silva
Dear all, I recently compiled squid-3.4.9 with ssl-bump support and, although it is working for the most part, I'm having some issues accessing some websites. The behavior is REALLY weird so I'm going to try and describe it the best I can: - If i access https://www.google.com/ in Chrome, I could