ased web filter server for Squid
proxy.
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Diogenes S. Jesus
Sent: Thursday, September 1, 2016 11:37 AM
To: Alex Rousskov
Cc: squid-users@lists.squid-cache.org; erdosain9
Subject: Re: [squid-users] HTTPS chrome - S
The answer why you only see it on Chrome is because since Chrome >= 41:
"Sites with end-entity certificates that expire on or after 1 January 2017,
and which include a SHA-1-based signature as part of the certificate chain,
will be treated as “affirmatively insecure”. Subresources from such domain
On 08/31/2016 09:15 AM, Amos Jeffries wrote:
> On 1/09/2016 2:26 a.m., erdosain9 wrote:
>> Hi.
>> Im using ssl-bump.. all ir working fine, but i want to know if it is
>> possible that which is not seen crossed out and red "https".
>> This happen just in Chrome
>> This page is insecure (broken HTTPS
On 1/09/2016 2:26 a.m., erdosain9 wrote:
> Hi.
> Im using ssl-bump.. all ir working fine, but i want to know if it is
> possible that which is not seen crossed out and red "https".
> This happen just in Chrome
> This page is insecure (broken HTTPS)
> SHA-1 Certificate
> The certificate for this sit
Hi.
Im using ssl-bump.. all ir working fine, but i want to know if it is
possible that which is not seen crossed out and red "https".
This happen just in Chrome
This page is insecure (broken HTTPS)
SHA-1 Certificate
The certificate for this site expires in 2017 or later, and the certificate
chain c
