On 2016-11-05 09:22, Amos Jeffries wrote:
On 5/11/2016 6:56 a.m., Garri Djavadyan wrote:
On 2016-11-04 19:42, Amos Jeffries wrote:
On 5/11/2016 1:43 a.m., Garri Djavadyan wrote:
The configuration for splice at step 3:
# diff etc/squid.conf.default etc/squid.conf
73a74,78
https_port 3129
On 5/11/2016 6:56 a.m., Garri Djavadyan wrote:
> On 2016-11-04 19:42, Amos Jeffries wrote:
>> On 5/11/2016 1:43 a.m., Garri Djavadyan wrote:
>>> The configuration for splice at step 3:
>>>
>>> # diff etc/squid.conf.default etc/squid.conf
>>> 73a74,78
https_port 3129 intercept ssl-bump
On 11/04/2016 08:06 AM, Garri Djavadyan wrote:
> On Fri, 2016-11-04 at 17:43 +0500, Garri Djavadyan wrote:
>> I noticed that Squid doesn't use gathered domain name information for
>> %ru in access.log when splice action is performed at step 3 for
>> intercepted traffic.
%ru is about client/user
On 2016-11-04 19:42, Amos Jeffries wrote:
On 5/11/2016 1:43 a.m., Garri Djavadyan wrote:
The configuration for splice at step 3:
# diff etc/squid.conf.default etc/squid.conf
73a74,78
https_port 3129 intercept ssl-bump cert=etc/ssl_cert/myCA.pem
generate-host-certificates
acl StepSplice
On 5/11/2016 1:43 a.m., Garri Djavadyan wrote:
> The configuration for splice at step 3:
>
> # diff etc/squid.conf.default etc/squid.conf
> 73a74,78
>> https_port 3129 intercept ssl-bump cert=etc/ssl_cert/myCA.pem
> generate-host-certificates
>> acl StepSplice at_step SslBump3
>> ssl_bump splice
On Fri, 2016-11-04 at 17:43 +0500, Garri Djavadyan wrote:
> I noticed that Squid doesn't use gathered domain name information for
> %ru in access.log when splice action is performed at step 3 for
> intercepted traffic. The format code ssl::>sni is available at both
> steps. Below are examples used
I noticed that Squid doesn't use gathered domain name information for
%ru in access.log when splice action is performed at step 3 for
intercepted traffic. The format code ssl::>sni is available at both
steps. Below are examples used to verify the behavior using Squid
3.5.22, but the results are