Oops. You shouldn't do this to every file; only on directories. Check the archives of this list for a more complete discussion. The following link gives a good description: <http://www.mail-archive.c
CVS 1.11.5 adds a major server-side security fix; you should upgrade. On the server, run 'chmod -R g+s YOUR_DIR'. This will "turn on" the set-group-ID bit so new files will be created with the same g
It's simpler than that: don't use NFS and the :local: access method. Just say no. I've been on CVS lists for years now, and I don't remember a single case of repository corruption that didn't involv
because that is what I read off of the website in ~Dec 21 2000 and had worked since. With a root of :pserver:address@hidden:/home2/cvsroot and its module name was also ccvs. I think we discussed this
I don't think so -- why are you looking for /home2/cvsroot? The correct CVSROOT for access to the current development version of cvs is (and the module name is ccvs). -Larry Jones I thought my life w
I have updated the permissions patch to version 1.11.5. Because the security problems in 1.11.4, you should update immediately. In case you don't know, this patch adds the following: * directory/file
Yes. The PuTTY documentation <http://www.chiark.greenend.org.uk/~sgtatham/putty/docs.html> includes everything you should need for the authentication and connection end of things. I'm using WinCVS 1.
Hi Kenneth, We're using pserver with Windows 2000 and CVSNT, connecting to multiple repositories using a little tool which sets the CVS environment variables for the command prompt. We go through an
We started down this path but couldn't get it working on Windows with cygwin ssh. (Server is a Red Hat box, though.) Is there a cookbook somewhere that explains how to make that scenario work? For ot
It also eliminates the ability to use the system's access controls to control access to your repository, not to mention any ability to track any particular action back to a specific user based on the
I just read the relevant section. Basically, CVS has its own password file, but will use the system password file as a backup. (This can be disabled.) The CVS password file uses a triplet of informat
Hi, But can patch be run in such a way that it generates conflict markers instead of .rej files? This would be very useful at times. Or is diff3 the go here instead? cheers, matt --Original Message--
Look on the bright side. There are very few bad choices here. CVS does nicely with JSP, Java, and HTML files. The one thing you might want to watch out for is that, if you like messing with the pack
I've been placed in charge of getting version control/management going at an organisation where I work. Right now, an almost anarchic situation exists where there is no real version control, several
Once you're connected to a pserver, it's a fairly simple process to get it to execute arbitrary commands for you; giving someone pserver access is equivalent to giving them shell access. s/pserver/s
I recently set up a remote access repository using a third method, which may help: Method 3: description: - users SSH into a single existing account. - Account is set up using a restricted shell (act
Perhaps I'm naive, but the recent posts describing local accounts (e.g. cvsphil) with no shell and ssh access to only the cvs command sound promising. Do you see anything specifically flawed with thi
Once you're connected to a pserver, it's a fairly simple process to get it to execute arbitrary commands for you; giving someone pserver access is equivalent to giving them shell access. -Larry Jones
I think we need to differentiate between "really bullet-proof security" and "reasonable security" - after all, security is also there to protect users from themselves, with no malicious intent requir