[squid-users] Fwd: Fwd: SSLBUMP Issue with SSL websites

From: Amit Pasari-Xsinfoways <ceo_at_xsinfoways.com>
Date: Sun, 11 Mar 2012 22:46:05 +0530

Dear All,
I have configured SSLBUMP in squid3.1 , in transparent mode for port 80
and 443 . My problem is when i open website like mail.yahoo.com or
gmail.com
it doesnt show me images , or when i open https://facebook.com
everything comes inline , no css nothing .
Where as when i configure my browser to use squid everything seems to be ok

My Details :
OS : Centos 4.8
Squid : squid3-3.1.8-1.el4
Squid.conf as below :
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
#acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
#acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
#acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged)
machines

acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
#acl SSL method CONNECT
acl newclient src 192.168.1.1-192.168.1.254
acl newclient1 src 10.0.0.1-10.0.0.254
acl publicip src 202.91.83.25-202.91.83.30

#
# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager

# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
#http_access allow localnet
http_access allow localhost

# And finally deny all other access to this proxy
http_access allow newclient
http_access allow newclient1
http_access allow publicip
http_access deny all

# Squid normally listens to port 3128
# http_port 3128
# Amit Start

always_direct allow all
ssl_bump allow all
sslproxy_cert_error allow all
http_port 3128 intercept ssl-bump cert=/etc/squid/server.crt
key=/etc/squid/server.Key

#the below should be placed on a single line
https_port 3129 intercept ssl-bump cert=/etc/squid/server.crt
key=/etc/squid/server.Key allow-direct options=NO_SSLv2

sslproxy_flags DONT_VERIFY_PEER
# Amit end
# We recommend you to use at least the following line.
hierarchy_stoplist cgi-bin ? xsinfoways.com
cache_mem 96 MB
cache_dir ufs /var/spool/squid 2000 16 256
request_body_max_size 0 KB

# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /var/cache/squid 100 16 256

# Leave coredumps in the first cache dir
coredump_dir /var/cache/squid

# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320

cache_effective_user squid
cache_effective_group squid

Some Errors in cache.log :

2012/03/10 17:41:44| clientNegotiateSSL: Error negotiating SSL
connection on FD 47: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol (1/-1)
2012/03/10 17:41:44| clientNegotiateSSL: Error negotiating SSL
connection on FD 47: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol (1/-1)
2012/03/10 17:44:04| clientNegotiateSSL: Error negotiating SSL
connection on FD 127: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol (1/-1)
2012/03/10 17:44:04| clientNegotiateSSL: Error negotiating SSL
connection on FD 128: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol (1/-1)
2012/03/10 17:44:04| clientNegotiateSSL: Error negotiating SSL
connection on FD 127: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol (1/-1)
2012/03/10 17:44:51| clientNegotiateSSL: Error negotiating SSL
connection on FD 21: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2012/03/10 17:44:51| clientNegotiateSSL: Error negotiating SSL
connection on FD 103: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2012/03/10 17:44:51| clientNegotiateSSL: Error negotiating SSL
connection on FD 103: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2012/03/10 17:44:51| clientNegotiateSSL: Error negotiating SSL
connection on FD 25: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2012/03/10 17:45:00| clientNegotiateSSL: Error negotiating SSL
connection on FD 20: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2012/03/10 17:45:00| clientNegotiateSSL: Error negotiating SSL
connection on FD 21: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2012/03/10 17:45:00| clientNegotiateSSL: Error negotiating SSL
connection on FD 70: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1
alert unknown ca (1/0)
2012/03/10 17:46:46| clientNegotiateSSL: Error negotiating SSL
connection on FD 56: error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol (1/-1)

Amit
Received on Sun Mar 11 2012 - 17:16:16 MDT

This archive was generated by hypermail 2.2.0 : Mon Mar 12 2012 - 12:00:04 MDT