On 12/04/2014 5:23 p.m., Amm wrote:
Hello,
I accidentally came across this. I was trying to test what TLS version
my squid reports.
So I ran this command:
openssl s_client -connect 192.168.1.2:8081
where 8081 is https_port on which squid runs. (with sslbump)
And BOOM, squid went in
On 04/13/2014 04:27 PM, Amos Jeffries wrote:
On 12/04/2014 5:23 p.m., Amm wrote:
So I ran this command:
openssl s_client -connect 192.168.1.2:8081
where 8081 is https_port on which squid runs. (with sslbump)
And BOOM, squid went in to infinite loop! And started running out of
file
Why https_port? and why ssl_bump on https_port ?
it should run ontop of http_port as far as I can understand and know.
There was an issue which I reported about and which is similar and I
have used couple acls to block the access and the loop from the port to
itself.
Eliezer
On 04/13/2014
On 04/13/2014 08:35 PM, Eliezer Croitoru wrote:
Why https_port? and why ssl_bump on https_port ?
it should run ontop of http_port as far as I can understand and know.
https_port is needed when you intercept port 443 traffic.
http_port intercepts port 80 and https_port intercepts port 443.
Hello,
I accidentally came across this. I was trying to test what TLS version
my squid reports.
So I ran this command:
openssl s_client -connect 192.168.1.2:8081
where 8081 is https_port on which squid runs. (with sslbump)
And BOOM, squid went in to infinite loop! And started running out of
