On 12/07/2015 8:16 a.m., Yuri Voinov wrote:
>
> Yep, man.
>
> Sad, but true.
No man.
[sorry, sent the followup in private by mistake. Repeating now for
everyone ... with a bit more info]
The TAG_* is a representation of what Squid has done in processing
the transaction.
We dont yet have tags/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yep, man.
Sad, but true.
11.07.15 16:13, David Touzeau пишет:
> To understand what you says:
>
> Means that squid try to understand the TLS protocol in order to
retrieve certificate information but some TAGS in certificate are not
properly unders
To understand what you says:
Means that squid try to understand the TLS protocol in order to retrieve
certificate information but some TAGS in certificate are not properly
understood.
So Squid still accept/forward the connection without decoding TLS ?
Le 11/07/2015 11:33, Amos Jeffries a écri
On 11/07/2015 9:23 p.m., David Touzeau wrote:
> Hi all
>
>
> We using Squid 3.5.6 in transparent mode with SSL
>
>
> With the following settings:
>
> acl ssl_step1 at_step SslBump1
> acl ssl_step2 at_step SslBump2
> acl ssl_step3 at_step SslBump3
> ssl_bump peek ssl_step1
> ssl_bump splice all
Hi all
We using Squid 3.5.6 in transparent mode with SSL
With the following settings:
acl ssl_step1 at_step SslBump1
acl ssl_step2 at_step SslBump2
acl ssl_step3 at_step SslBump3
ssl_bump peek ssl_step1
ssl_bump splice all
We have many entries "TAG_NONE/" in access.log when accessing to
