[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Secure Connections

From: Thornley, David
Subject: RE: Secure Connections
Date: Tue, 15 May 2001 09:35:19 -0500

> -----Original Message-----
> From: Echlin, Michael [mailto:address@hidden
> Sent: Monday, May 14, 2001 3:38 PM
> To: 'Santimore, Matt'
> Cc: 'address@hidden'
> Subject: RE: Secure Connections
> Hi,
> As someone else has already said pserver will use the unix 
> login passwords
> of anyone who is a user on that unix server. Set-up all of 
> your wincvs users
> as users on your server and put them in the right group to 
> see your cvs
> repository.

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.

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?

(For example, I've logged in for my own account, CVS/Root file
being :pserver:address@hidden:/..., and now I have to review Roland's code.
Roland's code is in his directory, CVS/Root file :pserver:address@hidden:/...,
and before I do a "cvs diff -u" I have to "cvs login".  Fortunately I
set up all the passwords the same, so it's no big deal.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]