info-cvs
[Top][All Lists]
Advanced

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

Re: what's to stop a developer from nuking the repository?


From: johnny fulcrum
Subject: Re: what's to stop a developer from nuking the repository?
Date: Tue, 20 Jan 2004 14:02:19 -0600
User-agent: Opera7.23/Win32 M2 build 3227

On Tue, 20 Jan 2004 14:08:45 -0500 (EST), Greg A. Woods <address@hidden> wrote:

[ On Tuesday, January 20, 2004 at 11:03:38 (-0500), Larry Jones wrote: ]
Subject: Re: what's to stop a developer from nuking the repository?

I think that's still overstating the case.  If you run CVS on a network
where you can trust people enough that you're confortable running
telnet or rlogin, then pserver is fine.

Telnet and rlogin and similar still provide on heck of a lot more
accountability (over a trusted network) than pserver could ever possibly
do.


Is there more than one way to run Pserver? All my pserver users have accounts on the unix box (err "unix network") and they have to suplly a username and password to "cvs login" (most of them are wincvs users).

how does this not give the same accountability as telnet or rlogin? everything they do has their username/group on it (commits adds etc)

Maybe I missed the boat somewhere, but I don't get how this is different than if they werre on the box using local cvs commands and no pserver connection.

If you have a trusted network and you do feel comfortable with telnet
and rlogin then USE THEM -- DO NOT USE PSERVER.




--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/




reply via email to

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