OK, now the architecture becomes clearer.  
after installation,
*) edit registry
*) run the service like
stunnel -d 83 -r www.targetserver.com:443
(d for daemon? all unix geeks :)

It may not be a solution that my remote client would accept though.
fumbling registry would not make him comfortable nor would he would be comfortable to let me to remote in to have a full control of his machine.
Why doesn't the installation take care of registry stuff?
thanks.

>Not quite like that....
>
>You would set stunnel up as a service following the instructions on the link
>below.
>
>http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:
>80/support/kb/articles/q137/8/90.asp
><http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com
>:80/support/kb/articles/q137/8/90.asp&NoWebContent=1> &NoWebContent=1
>
>If you Google for SrvAny then I'm sure you will find more links than
>this....
>
>You set stunnel up to listen on a port. For example lets say port 83. Then
>set all traffic to be forwarded to your destination server probably on port
>443....
>
>The command you would set up as a service should look something like this
>
>stunnel -d 83 -r www.targetserver.com:443
>
>Paul
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to