Difference between revisions of "Using encrypted channels to communicate with squid proxy server"

From Notes_Wiki
m
m
 
Line 1: Line 1:
<yambe:breadcrumb self="HTTPS proxy">Squid proxy server configuration|Squid</yambe:breadcrumb>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Squid proxy server configuration]] > [[Using encrypted channels to communicate with squid proxy server]]
=Using encrypted channels to communicate with squid proxy server=


We can use
We can use
Line 27: Line 26:
verify=3
verify=3
</pre>
</pre>
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Squid proxy server configuration]] > [[Using encrypted channels to communicate with squid proxy server]]

Latest revision as of 10:13, 14 July 2022

Home > CentOS > CentOS 6.x > Squid proxy server configuration > Using encrypted channels to communicate with squid proxy server

We can use 

https_port 8081 cert=/etc/squid/squid.pem

in 'squid.conf' to allow clients to connect to proxy using SSL, where 'squid.pem' can ge generated as explained at Openssl


On the client side we can use stunnel to tunnel all browser plain-text traffic over SSL to proxyserver, port 8081. Sample stunnel service configuration is 

	[facultyproxy]
	accept=8080
	client=yes
	connect=<proxy-ip-or-fqdn>:8081


We can add above section to '/etc/stunnel/stunnel.conf' file and run stunnel using 'stunnel /etc/stunnel/stunnel.conf' so that stunnel listens on port 8080 on localhost and forwards all incoming connections to proxy server on port 8081.


We can also add following options, if we have CA certificate and we want to defy man-in-the-middle attacks via other self-signed certificates. 

	CAfile=/etc/pki/CA/private/ca.crt
	verify=3


Home > CentOS > CentOS 6.x > Squid proxy server configuration > Using encrypted channels to communicate with squid proxy server

Retrieved from "http://www.sbarjatiya.com/notes_wiki/index.php?title=Using_encrypted_channels_to_communicate_with_squid_proxy_server&oldid=6475"