On Sat, Jan 25, 2003 at 02:42:51PM -0601, Dave Huang wrote:
> On Sat, Jan 25, 2003 at 02:29:45PM -0600, Richard Rauch wrote:
> > One way that this could be done is to set up a local program and another
> > on the same machine as the server software.  You would telnet to
> > the localhost (parameter to your client software, not a change to
> > it) and the local software wraps your message up in encryption and
> > sends it to its counterpart on the machine where the server process
> > lives.  The counterpart decrypts and does a localhost telnet.
> 
> Perhaps stunnel <http://www.stunnel.org/> will do what you want? I

Maybe.  Another gave me that pointer in private email earlier today.
(I also found stunnel in pkgsrc.)

I started to read a web-page on setting up stunnel with a client.
I assume that a non-SSL-aware server can be made to work with
stunnel at the other end.  (It would probably actually be better if
the server were able to tell apart the two types of connection in
some way.)

Another SSL tunnel was pointed out in a public reply, I see.


A small down side is that I assume that stunnel doesn't work for non-UNIX
people.  (I haven't read the docs, though.)  I'd wish for a general
solution, regardless of OS type, but there doesn't appear to be a lot of
choice about the options.

(What about IPSec?  Is this widely available if the server is set up
correctly?  Or does it require extra work on the client's side a well?)


Thanks for the pointer, though.  At least there is some hope.  (^&


-- 
  "I probably don't know what I'm talking about."  --rkr@olib.org