@lists.squid-cache.org
Subject: Re: [squid-users] SSL handshake
On 8/8/21 1:48 AM, senor wrote:
> Can you point to a patch under test or other changes that we can use
> to alleviate this pain?
I will probably regret sharing this unfinished work, but our current
changes can be found at [1]. A F
ix for the official review ASAP. My current
ballpark ETA for that is ~6 weeks.
HTH,
Alex.
> From: squid-users on behalf of
> Alex Rousskov
> Sent: Tuesday, August 3, 2021 1:04 PM
> To: squid-users@lists.squid-cache.org
> Subject: Re: [squid-users] SSL handshake
>
>
1:04 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] SSL handshake
FWIW, Factory can reproduce this (popular origin server) problem with
and without Squid. We are adding a Squid enhancement that will work
around the problem (and improve TLS support in general).
Alex.
> c
FWIW, Factory can reproduce this (popular origin server) problem with
and without Squid. We are adding a Squid enhancement that will work
around the problem (and improve TLS support in general).
Alex.
> curl: (35) error:1423506E:SSL routines:ssl_next_proto_validate:bad extension
Hi,
I don't know if my situation is like Nishant's, but today my issues have gone
away without intervention on my behalf.
I'm guessing the cause was on the remote server's side or some in-between SSL
inspection...
Thanks,
Vieri
___
squid-users mailin
On 27/07/21 9:15 pm, Vieri wrote:
>
> I have not changed anything in the OS so it might be because of change in the
> remote web service.
> It might be that my openssl version is already too old (1.1.1g), and that the
> web site forces the use of an unsupported cypher?
I have also observed it o
On 7/27/21 11:45 AM, Vieri wrote:
> Just recently I've noticed that LAN clients going through Squid with sslbump
> are all of a sudden unable to access certain HTTPS sites such as
> login.yahoo.com.
> The squid log has lines like:
>
> kid1| 4,3| Error.cc(22) update: recent:
> ERR_SECURE_CONNEC
