Experience in configuring user permissions for cvsnt

Experience in configuring user permissions for cvsnt

Szbruce77@163.com
There are too many projects in the company recently, and the code is too messy,
This article has basically been summarized, but it is easy for new users to make mistakes.
My cvsnt version is 2.5.03, WINXP. I didn't use the wincvs on 8848software.
There are always some problems (Python and Tcl are required to be installed, and there are many restrictions on the version, but some of his PDF documents are good, haha)

AA. After installing cvsnt, you need to use the program ---> cvsnt Control Panel to set the repository directory
D:/cvsroot name: cvsroot (this is equivalent to/cvsroot in a Unix name on the client later)
Do not use D:/cvsroot
BB. Then log on with the Windows user name, such as zpb (it is best to be administrator)
Cc.
Run
/*****************,
Add the CVS user name and password. The following command is required:

CVS passwd-r 'real username'-A 'cvs username'
'Real user' is the Windows user name.
'Cvs user' is the user name of CVS. You can configure the same real user for different CVS users.
After the preceding command is executed, a user name and password record will be added to the [$ {repository}/cvsroot/passwd] file on the server,
Format: User name: Encrypted Login Password: Windows system user + [Press enter]. Run the preceding command multiple times to add the CVS accounts of all project team members.
Create three new files in the [$ {repository}/cvsroot/] Directory: Admin, writers, readers,
As the name suggests, these three files are used to specify users who can perform corresponding operations on the cnsnt repository,
The format of these three files is: User Name + [Press enter]. Separate the accounts of the project team members added in 2 according to their Permissions
Write these three files. Add at least one account to the admin file as the administrator.
/*****************,
Note that:
For example, I have a user in writers, testwriter zpb xxj.
If you want to add xxj as admin, make sure that xxj exists in writers.
Otherwise, CVS passwd-r 'real username'-A 'cvs username'
The system always prompts that users cannot be added, and passwd cannot be written.
CVS [server aborted]: "passwd" requires write access to the repository

 

Http://blog.csdn.net/jjdragon/archive/2006/10/26/1352218.aspx
Step-by-step configuration of cvsnt Access Permissions
By default, cvsnt manages the permissions of users in Windows as their own users. To separate CVS users from Windows users,
Some settings are required for managing your user permissions by cvsnt. The following is a convenient configuration procedure:

(In this article, $ {repository} is used to represent the repository path of cnsnt)

(The cvsnt version used in this article is 2.0.51d. The command used may be different from the new version)

 
1. Add a system user cvsuser to the Windows system where cvsnt is installed.

 

2. Add the CVS user name and password. The following command is required:

CVS passwd-r 'real username'-A 'cvs username'
'Real user' is the Windows user name.
'Cvs user' is the user name of CVS. You can configure the same real user for different CVS users.
After the preceding command is executed, a user name and password record will be added to the [$ {repository}/cvsroot/passwd] file on the server,
Format: User name: Encrypted Login Password: Windows system user + [Press enter]. Run the preceding command multiple times to add the CVS accounts of all project team members.
3. Create three new files in the [$ {repository}/cvsroot/] Directory: Admin, writers, and readers,
As the name suggests, these three files are used to specify users who can perform corresponding operations on the cnsnt repository,
The format of these three files is: User Name + [Press enter]. Separate the accounts of the project team members added in 2 according to their Permissions
Write these three files. Add at least one account to the admin file as the administrator.

 

4. Switch the cvsnt permission authentication method. As mentioned above, cvsnt uses Windows as its own user by default,
Now it is easy to change the permission authentication method,
Change systemauth = yes in the [$ {repository}/cvsroot/config] file to systemauth = No.
In this case, the original Windows account cannot access the CVS server, and only the Account Added in 2 can access it.

 

5. In the above four steps, the read, write, and management permissions of the entire repository of CVs are configured. However, we know that the repository can also be implemented
Divided into projects, modules, files, and other levels. Project management requires more detailed permission settings for these projects, modules, and files. To implement this function, the following command is required:

CVS chacl {user}: [{[r] [W] [c] | [N]}] [directory...]
First, use "CVS chacl default: N." To cancel the default user permission, and then add the required account permissions.
Remember: only the module owner can execute this command. After executing this command, a record is added to the. perms file of this module.
Only users added to this file have read and write permissions.

6. After completing the above work, the basic goal has been achieved, but there is another vulnerability that needs to be supplemented,
Because CVS uses related files in the [$ {repository}/cvsroot/] Directory to record permission information,
If a user in the writers file checks out these files and then checks in after modification, the access permission of CVS is controlled.
To block this vulnerability, use the method in step 5 to restrict access to [$ {repository}/cvsroot/], so that the administrator can only read and write the directory.
(Through the CVS Co cvsroot project, I found that some control files cannot be found in the new version. It seems that 2.5 has solved the bug)

 

Trackback: http://tb.blog.csdn.net/TrackBack.aspx? Postid = 1352218