|
-----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 understood. > So Squid still accept/forward the connection without decoding TLS ? > > Le 11/07/2015 11:33, Amos Jeffries a écrit : >> 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 >>> >>> >>> We have many entries "TAG_NONE/XXXX" in access.log when accessing to SSL >>> websites. >>> >>> What does it means ? >> Spliced connection. No HTTP handling occured. >> >> The TLS logics do not yet have proper processing tags defined yet. That >> is still on the todo list. >> >> Amos >> >> _______________________________________________ >> squid-users mailing list >> squid-users@xxxxxxxxxxxxxxxxxxxxx >> http://lists.squid-cache.org/listinfo/squid-users > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVoXm5AAoJENNXIZxhPexG6TUH/2H02D3FXynZ1Y2lngkEhDD3 ov8I4uujWwAEW9cmaoNqWCcewO/8gOzxa46dTntxnFi8Zun6/C88bWSVedBmcGN5 4hjjdQjnIO7D1aT+ehp0ozW2TrXJcy2IYx/9S5tZuWLByz77YTjyau+e+4Eym3/H rjEzX8yQjBJiWhl4ihMn9Xl3LLBBRsidDmaTNPpNAWhUBJcR5SYQ54LitNdWJjTe I3eIyzU7UlInjhCD4VFhyuuT2lwXSsD8HrLPSaLalenZNeeFMofw6h3NHibyYENa zyNgPMp8pHXcok2+ipY5I0wGYoXTpbncRry45G4ae9wQJhuPZsULI2pB2ToHWUQ= =EQ9v -----END PGP SIGNATURE----- |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
