AFAIK there are three approaches:
The most common is to run the server in 'ssh mode' where the clients
ALWAYS talk to the server with ssh (or rsh possibly if your network is
already secure enough) for all traffic. ssh handles the authentication, and
the cvs on the server assumes you are good if you got that far.
The other possibility is to tunnel the pserver over ssh, which most
people would consider outright silly, since you can just 'run the server'
native in ssh mode.
The third I believe involves a kerberos aware CVS, of which I have no
experience or knowledge in.
----- Original Message -----
From: "Gregory Propf" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 12, 2000 12:59 PM
Subject: CVS security
> I'm new to the list. My name is Gregory Propf and I'm a programmer in
> Florida, USA. I'm trying to coordinate programming efforts across
> multiple developers who write code offsite. I would like to use cvs but
> am concerned about security. I've played around with Kerberos but can't
> get it working. Mainly, what I would like is just to have cvs talk over
> a secure socket so that usernames and passwords are encrypted. Is there
> a way to do this? I have used ssh to do port forwarding for cvs but the
> result is a kludge.
>
>
>
>
>
>
>
> --
> With every passing hour our solar system comes forty-three thousand
> miles closer to globular cluster M13 in the constellation Hercules, and
> still there are some misfits who continue to insist that there is no
> such thing as progress.
> -- Ransom K. Ferm
>
>
