--- Brandon Brinkley <[EMAIL PROTECTED]> wrote:
> 1. Can CVS be made more hack-proof (e.g. owner permissions on RCS files in > the CVSROOT)? create a pserver account, a cvs admin account, a cvsrepo group and put only those two accounts in that group. run pserver as the non-root pserver account, create repos (775) with the cvsadmin account. now no accounts but these two accounts have access to the physical CVS repository structure. When you create the repo, chmod 755 the CVSROOT directory. All users must now use CVS (in pserver mode) to change anything in the repository, you can use the cvs admin account in local mode to change CVSROOT. Sure you hav eto maintain a passwd file, but I find that easier that maintaining a sticky bit/SGID/group balance in the repository. > 2. Can tags be made permanent (no deletions or reuse)? A simple taginfo script can do this. We have a script that requires the admin to create/move/delete any tag that starts with 'cm'. If you need to be more restrictive that that, you can obviously by the script you write. > Based on what I've read, I don't expect either exercise to be a trivial > undertaking, but I'd be very interested in hearing success stories, ideas, > possible approaches, etc. > > Thanks much. > -Brandon > __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
