What is the best approach to implement access control on CVS repositories hosted on a Linux server? The goal is to prevent accidental deletion of modules by developers. The developers should be able to do all other CVS activities.
+1
A:
Use SSH access: howto cvs-ssh, other howto
It also looks like you're trying to give them a shell? And access to a CVS repository filesystem? If yes, then it isn't necessary. They do not need access to repo filesystem to do all standard CVS activities.
A:
mount ro? No but seriously, if you prevent module deletion, there is still nothing preventing them from deleting the content of the module, so I don't really understand the question. What should they be able to do precisely?
disown
2009-05-15 17:16:34
A:
CVSACL is a patch for CVS. It adds two new subcommands (acl & racl) to cvs for access control list management.
CodeLizard
2009-05-15 20:07:43