Question

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.

Was it helpful?

Solution 2

CVSACL is a patch for CVS. It adds two new subcommands (acl & racl) to cvs for access control list management.

http://cvsacl.sourceforge.net/

OTHER TIPS

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.

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?

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top