On 14/08/20 3:01 am, mabi wrote:
> ‐‐‐ Original Message ‐‐‐
> On Thursday, August 13, 2020 3:13 PM, Alex Rousskov
> wrote:
>
>> On 8/13/20 6:24 AM, mabi wrote:
>
>> You probably need a fix for TLS GREASEd values. Here is its v4 flavor:
>>
>> https://github.com/squid-cache/squid/commit/f
‐‐‐ Original Message ‐‐‐
On Thursday, August 13, 2020 3:13 PM, Alex Rousskov
wrote:
> On 8/13/20 6:24 AM, mabi wrote:
> You probably need a fix for TLS GREASEd values. Here is its v4 flavor:
>
> https://github.com/squid-cache/squid/commit/f7a315f.patch
Thank you for the hint. Do you kn
Dear Erick,
Thank you for your answer.
I tried accessing chrome://flags/#tls13-variant but nothing appears. If I
search for a flag containing TLS the only one is #enforce-tls13-downgrade. This
is my Chrome version:
Version 73.0.3683.75 (Developer Build) built on Debian 9.8, running on Debian
Hello,
I am using Squid as transparent proxy for HTTP and HTTPS traffic on an OpenBSD
6.7 firewall. Since I have upgraded from Squid version 4.11 to 4.12 my Chrome
browser is not able to visit any HTTPS websites. Firefox continues to work fine.
Older versions of Chrome show a ERR_SSL_VERSION_I
On 8/13/20 6:24 AM, mabi wrote:
> Since I have upgraded from Squid version 4.11 to 4.12 my Chrome
> browser is not able to visit any HTTPS websites. Firefox continues to
> work fine.
You probably need a fix for TLS GREASEd values. Here is its v4 flavor:
https://github.com/squid-cache/squid/c
Just a quick question Mabi,
in chrome address bar please type chrome://flags/#tls13-variant
what tells you about TLS and QUIC?
do you have any nonstandard value?
By any chance can you share the (potentially) offending website?
thanks.
On Thu, Aug 13, 2020 at 5:25 AM mabi wrote:
> Hello,
>
> I a
