--- Brandon Brinkley <[EMAIL PROTECTED]> wrote: > 1. Can CVS be made more hack-proof (e.g. owner > permissions on RCS files in > the CVSROOT)?
Depending on how much protection you want, you can: 1. Use the usual file permissioning to prevent unwanted people from reading/writing to the files/repository. 2. Use POSIX ACLs to prevent unwanted people from reading/writing to the files/repository. 3. Use SSH to force users to use CVS to access the repository. > 2. Can tags be made permanent (no deletions or > reuse)? I think there might be a patch out there for this. OTOH, since tags reside within the RCS files, you'll need to manage the RCS file access as well. > 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. It really depends on exactly what you want to do. Can you be a little more specific in your requirements? Noel __________________________________________________ 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
