[stunnel-users] Feature request: set environment variable for inetd-type program
Claus.Lund at state.vt.us
Fri Jan 23 20:30:12 CET 2009
I'm not a developer on stunnel so my opinion doesn't carry much weight :-)
But, to me, this seems a bit outside the scope of what's stunnel's main goal in life. Why not just have that authentication handled between the client and server programs using the tunnel stunnel provides? Or maybe I just don't quite get what you're trying to accomplish (a totally plausible option!).
From: stunnel-users-bounces at mirt.net [mailto:stunnel-users-bounces at mirt.net] On Behalf Of Michael Renner
Sent: Friday, January 23, 2009 1:34 PM
To: stunnel-users at mirt.net
Subject: [stunnel-users] Feature request: set environment variable for inetd-type program
I am not a programmer, I am a writer and user, so I have to ask kindly for a
additional stunnel feature
I need the ability to push some information from the stunnel client side to
the server side. To be more concrete: a self written script that is called by
stunnels 'exec' statement need some settings, e.g. username and password. My
idea is to configure this in the client side stunnel.conf and pass this as a
environment variable to this script.
There is no chance to pack these stings in a client certificate, because
everybody who is able to handle snoop/tcpdump will be able to read this.
I imagine a configuration like this:
accept = 127.0.0.1:1234
connect = 184.108.40.206:443
env = "SUSER=renner"
env = "SPASS=geheim"
accept = 220.127.116.11:443
exec = /opt/foo/script.sh
env = yes
My question to the developers: do you think this is a helpful feature, also
|Michael Renner E-mail: michael.renner at gmx.de |
|D-81541 Munich Germany ICQ: #112280325 |
|Germany Don't drink as root! ESC:wq
stunnel-users mailing list
stunnel-users at mirt.net
More information about the stunnel-users