Re: [squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-20 Thread pius
Thanks for the reply. That really helped. I had an ACL for network and that blocked the https traffic coming through. It has been a journey settling it up. But without you guys help I think I was not able to do it. Thanks for all help. Much appreciated. Few settings that help with debugging and

Re: [squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-17 Thread pius
Hi Amos, Thanks for the reply. It makes more things clear. I do apologize for a Friday message in advance. I will explain a bit more about my situation. We are using Jfrog artifactory in our private network. Artifactory host lots of remote repos. We are planning lock down the artifactory using

Re: [squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-16 Thread pius
Hi, We are planning to control the traffic that goes out from the network. Few of them are HTTPS. we managed to whitelist HTTP traffic that going out the network. And we are really happy about it. Now only worry we got is the HTTPS traffic. I listen 2 port in squid. 3129(HTTP) and 3130 (HTTPS).

Re: [squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-13 Thread pius
Hi, It will be great if anybody can help. I can see that the client can talk to squid and squid communicating to google. But it responding with an error. ## Curl Log # ]# curl https://www.google.com -iv * About to connect() to www.google.com port 443 (#0) * Trying 216.58.204.68... *

Re: [squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-13 Thread pius
Hi, I made some improvement. I added "ssl_bump splice all" and now it passing through the step 1, but I can't whitelist the domain I want to connect through the squid now. I am getting a new error ## cache.log ### 2018/08/13 13:37:02 kid1| SECURITY ALERT: Host header forgery detecte

Re: [squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-13 Thread pius
Hi, Thanks for the reply. I haven't got access to log on weekend, sorry about the late reply. I google about this error. I got some answer like connect message is in plain text and squid is expecting a TCP communication and it gets rejected in lower level before getting to step 2. I am not sure t

Re: [squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-10 Thread pius
Hi, Thanks for the reply. I had an ACL whitelist for IPs. I tried the test again removing that. Now I get an error TAG_NONE/200 0 CONNECT. Still, I am not getting server IP or domain name and got squid IP instead. (10.222.17.106:3130). Does that mean, the request is still blocked in step 1 O

[squid-users] Have issue with "https_port ssl-bump intercept"

2018-08-10 Thread pius
I am getting IP address of the client instead of the domain name I requested. I am trying curl -iv https://www.google.com from a client machine (10.222.17.106). I am not getting google.com in the access log and getting TCP_DENIED. Looks like traffic is blocked before checking the certificate( I a