[inbound]
accept =
5102
connect =
5010
[outbound]
accept =
5101
connect =
x.x.x.x:5102
The first STunnel
example on the website talks about doing this, sort of, but I don't see any
options to specify on a service configuration level whether the listen port is
in SSL or non-SSL mode. The use of a service name like [pop3] vs [pop3s] seems
to imply a difference, but I've got a custom application I'm trying to tunnel
two way, not a standard IETF service.
A perusal of the
last year's mailing list archives didn't yield anything. I guess the next step
is to look at the source and see if it's supported unless someone here can tell
me one way or the other. If it's not supported, I guess I'll add it
in.
thanks,
Paul