[stunnel-users] issue making stunnel 4.35 use an apache http proxy to go out?

Matt Wise mwise at netflix.com
Fri Apr 8 18:26:53 CEST 2011


I've got an Apache proxy on port 3128 that will allow our clients to get outbound with a 'CONNECT" to a few services.. I'm trying to make stunnel use this service, and it seems to be ignoring my configuration completely. Tcpdumps show NO packets going outbound on port 3128... any ideas what i'm doing wrong? This config allows an inbound connection to port 1234 to hit port 2345  (a local service), while also handling the setup of an inbound connection to localhost:514 to a remote host on port 1514... 

debug = 7
pid = /var/run/stunnel.pid
service = stunnel
syslog = yes
foreground = no
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
fips = no

# Localhost:1234 hits localhost:2345
[cseservices]
client = no
accept = 1234
connect = 127.0.0.1:2345
CAfile = /etc/stunnel/ssl/tunnel-CAs.cert.pem
cert = /etc/stunnel/ssl/server.pub
key = /etc/stunnel/ssl/server.key
verify = 2

## Localhost:514 hits remotehost:1514
[syslog]
client = yes
accept = 514
connect = xxx:1514
CAfile = /var/lib/puppet/ssl/certs/ca.pem
key = /var/lib/puppet/ssl/private_keys/xxx.pem
cert = /var/lib/puppet/ssl/certs/xxx.pem
session = 5
TIMEOUTidle = 600
TIMEOUTbusy = 600
TIMEOUTclose = 300
TIMEOUTconnect = 10
verify = 2
protocol=connect
protocolHost=proxy:3128
protocolAuthentication=basic

—Matt





More information about the stunnel-users mailing list