On Apr 14, 2015, at 3:40 PM, Stakres vdoc...@neuf.fr wrote:
Hi All,
No reply ?
Do we have to leave with this mega/crazy bug ?
Is there someone in the Squid team able to have a look to this problem or
nobody care ?
Thanks in advance.
Bye Fred
The issue I’m aware of (bug 4212)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Don't think this is critical. What is native fs block size?
09.04.15 13:29, Stakres пишет:
Hi Yuri,
We have checked the sslproxy_capath, all certifs updated.
OpenSSL is: OpenSSL 1.0.1e 11 Feb 2013 (Debian 7.8)
Additional point, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Don't think this is critical. What is native fs block size?
09.04.15 13:29, Stakres пишет:
Hi Yuri,
We have checked the sslproxy_capath, all certifs updated.
OpenSSL is: OpenSSL 1.0.1e 11 Feb 2013 (Debian 7.8)
Additional point, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Note: This line:
ssl_bump server-first all
in config is from 3.4.x, in 3.5.x you must use new bump syntax.
Also:
- -what openssl/gnutls version used to build squid?
- -Is sslproxy_capath contains really complete set of root/intermediate
CA's
As I can research,
this problem produces one of Apple service under HTTPS.
When client query something like iTunes, squid gets strange certificate
which is corrupts DB.
I found no solution at this time. Just stop squid and cleanup SSL db.
WBR, Yuri
18.03.15 11:21, Dan Charlesworth пишет:
Bumpity bump
Had this go down exactly the same way this past Monday at Deployment #1.
On 10 Mar 2015, at 4:51 pm, Dan Charlesworth d...@getbusi.com wrote:
Hey folks
After having many of our systems running Squid 3.4.12 for a couple of weeks
now we had two different deployments fail
Hey folks
After having many of our systems running Squid 3.4.12 for a couple of weeks now
we had two different deployments fail today due to SSL DB corruption.
Never seen this in almost 9 months of SSL bump being in production and there
were no problems in either cache log until the “wrong
