handling cvspasswd in presence of several virtual repositories
Brought to you by:
tyranny
From: Alexey M. <al...@hs...> - 2001-11-18 23:43:11
|
Current installation instruction suggest to make the 'cvspasswd' binary setgid reposNadmin, thus enabling the ordinary users to change their passwords. This scheme is obviously broken, because there are many reposNadmin's. Here is the solution: + Regarding several repositories. You should create a pair of user-group accounts on server machine. Let them be called simply: repos1.repos1, repos2.repos2 and so on. How to handle several repositories wrt 'cvspasswd' program: We could create the appropriate users and groups: repos1admin.repos1admin, repos2admin.repos2admin, etc. The 'cvspasswd' program gets installed setuid root. There is a hardcoded configuration file /etc/cvspasswd.conf, containing lines like: /repos1 repos1admin:repos1admin /repos2 repos2admin:repos2admin /repos3 repos3admin:repos3admin When the cvspasswd program is run by the ordinary user (running under repoN.reposN, where every reposN user is in the 'cvs' group), it reads the configuration file and setuids to the appropriate user/group. Afterwards it modifies the CVSROOT/cvspasswd file. This probably should be made the default behaviour. --alexm |