[ On Tuesday, May 15, 2001 at 09:35:19 (-0500), Thornley, David wrote: ]
> Subject: RE: Secure Connections
>
> I felt very uncomfortable in doing that, since it leaves the unix
> passwords hanging out in the open, albeit in encrypted form. I
> simply assigned a standard CVS password and told people to use that.
> I have no qualms about leaving CVS insecure, because I figure CVS
> is insecure, and there are other ways to limit access.
You should only use SSH then.
> BTW, I've run into an inconvenience. In the process of checking over
> one another's code, we're constantly using CVS in other people's
> directories (primarily "cvs diff"). Is there a way to avoid having
> to "cvs login" in every new account accessed, since the trees in
> different people's accounts have different CVS/Roots now?
I don't think it would be a problem if you were using SSH and RSAHost
authentication (i.e. ~/.shosts or ~/.rhosts).
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
