I'd like to invoke stunnel to handle a single SSL client-side connection (talking to an SSL server) with the assurance that the stunnel quit will automatically quit after that one connection closes. I did not see any options to support this. Did I overlook something, or is stunnel just not able to do this?
D. Richard Hipp drh@hwaci.com
On Jan 13, 2009, at 8:03 AM, D. Richard Hipp wrote:
I'd like to invoke stunnel to handle a single SSL client-side connection (talking to an SSL server) with the assurance that the stunnel quit will automatically quit after that one connection closes. I did not see any options to support this. Did I overlook something, or is stunnel just not able to do this?
Answer to my own question:
Apparently stunnel will work as a pipe if I create a config file like this:
client=yes connect=remosthost:port
Then run stunnel and talk over standard input and standard output.
D. Richard Hipp drh@hwaci.com
stunnel-users mailing list stunnel-users@mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users
D. Richard Hipp drh@hwaci.com