Stunnel.org

Protecting CVS with Stunnel

First, is there a reason you want to use Stunnel? In most cases it'd be easier to use SSH if it's available on both ends. For example:

	$ CVS_RSH=ssh
	$ export CVS_RSH
	$ cvs -d cvs-server.example.com:/path/to/cvs/root cvs co ...

This requires that you have a login to the remote machine, of course. If you have other arguments needed on the ssh command line you could put them in the CVS_RSH variable too:

	$ CVS_RSH="ssh -l myremoteusername -C"

The above forces the remote username, and enables compression, for example. Or you could create appropriate entries in ~/.ssh/config to handle all this seemlessly.

--bri

Date: Wed, 29 Aug 2001 10:20:31 -0700 (PDT)
From: Adam Shand <adam at personaltelco.net>

I'm using stunnel to wrap cvs traffic.  I'm running stunnel 1.14 (the debian
package) on the server like this:

https   stream  tcp     nowait.400      root    /usr/sbin/stunnel stunnel -T -l /usr/sbin/cvs-pserver

On my laptop using the debian package of stunnel I run
Stunnel like this:

# stunnel -c -r cvscust.pixelworks.com:443 -d 2401