Hi!
we had the same problem when we switched from openssl 1.1 to openssl 3 with
certificates using the SHA1 algorithm for signature. The reason for this was in
openssl 3 SHA1 is deprecated.
Kind regards,
​Hannes
Von: squid-users
Gesendet: Dienstag, 11. Juli 2023 19:34
An: squid-users@lists.sq
Hi guys!
I had a similar problem with bumping the SSL connections.
When I did a ssl_bump stare at the step SslBump1 and then a ssl_bump bump all
the site did not load at all until I removed the ssl_bump stare. My futher
invenstigations took me to the ConnStateData::httpsPeeked method were the
co
hange server authentication via squid
reverse proxy not working after upgrade from squid 4.15 to 5.6
On 8/09/22 19:40, Hannes Fasching wrote:
> Hello,
> A customer have an issue that after upgrading from squid 4.15 to actual 5.6
> with reverse proxy mode for an exchange server.
> The
/EcPpd3DeeoFLs4_9Dn6JWAYBbHrwenOEJ3SZ0IW8_ED1-A?e=Ff9BZc
(squid_cache.log)
It would be great if you could help me finding out what is wrong with Windows
integrated authentication as our customer needs the SSO feature.
Thanks in advance and Kind regards,
Hannes Fasching
PS: All public/relevant IP's and domain names
is closing the server side and after detecting a "half closed" connection
squid is also closing the client side.
Also the "cache_peer" parameter "connection-auth=on" changes nothing.
Thanks in advance for your answer
​Hannes Fasching
Get the 13 E
