All of these operations-based environment and software versions: Windows2000 Pro, CVSNT2.0.4, WinCVS1.3.9.1Beta9 In the previous introduction CVSNT mood in line with WinCVS, the user-managed and authority allocation of CVSNT has been more detailed. Narrative, but there are still some concepts that have not been clear. Here, I will give a set of user management, authority management programs according to the actual needs of the project, and some of their own experiences, you are better to read before reading this article. A front article, an increase in users, the modification of permissions, etc. These operations can be understood, otherwise it will have a little difficult.
1. User verification mode of CVSNT We discussed here in the PServer mode.
Two authentication methods are given in the CVSNT documentation, I summarize it, you can call this: Window and CVSNT mixed verification methods, CVSNT independent verification mode. In the previous article, we have no detailed to give the contents of these two ways, the inspiration described is a mixed verification method.
Deciding that CVSNT works in the verification mode is determined by the CVS management file, which is in the cvsroot directory in the directory of the library, which can be concluded that for different libraries, you can give different verification methods. Therefore, when each library is established, it must first set these premise.
The following operations If there is no special pointing, it is managed on the client. The first is some instructions for some control principles and related files. If you are performing related simulation, stop temporarily stopping your operation. , Because the steps of these operations have been there, if you are not right, then you may fail to fail, don't have the following operations.
1.1 The CONFIG file has been established in the library. You have not modified the control file. CVSNT is under the mixed verification mode. At this time, the administrator of the CVS server is the administrator of CVSNT, you with one Administrator logins, check the CVSROOT module you want to operate, see the list of files, control the verification of CVSNT is the config file, you can find it in the list of files, double-click to see the content, here Our most important thing is the first setup content, you will see the following:
# Set this to `no 'if pserver shopn't check system users / passwords
# Systemauth = yes
The second line is what we want to modify, the default status is commented, SYSTEMAUTH has two values and NO
YES: PServer will use the system user database and passwd file (which will be detailed later) (this file will be described in detail) (if the Passwd file does not exist or there is no corresponding information in the file, verify using the system user) The default is YES.
NO: All users must exist in the passwd, according to the contents of the Passwd to perform the user's verification.
The solution I will be in this is to work below NO. After the modification, submit it to the server, and submit the server in the independent verification mode of CVSNT. In this working mode, NT local users and CVSNT users do not have any nature of contact and influence (just to create an alias).
1.2 Passwd file mentioned this file when it comes to the above, when the server works in the CVSNT verification mode, this file can be called CVSNT user database, which stores the list, the user's password, and Some information of alias. By default, this file does not exist, so if we want to work in CVSNT verification mode, this file must be established. Note: This file cannot be modified on the client. The content of this file is quite simple, like the following: Bach: Ultgrlxo7nRxs
SPWANG: 1SOP854GDF3DY
Melissa: TGX1FS8SUN6RY: PUBCVS
QProj: XR4EZCES0SZIK: PUBCVS
Here, take the first user BACH and the third user Melissa to explain that each line represents a user, with a total of three parts, user name, password, and local user three parts use a colon ":" to split.
Username: is the username of login CVS
Password: The user's password, here is encrypted, if it is empty, then the empty password
Local users: CVS users correspond to local users, (there is no other relationship with local users, just alias relationships)
If there is a username Bash in the local system, it is necessary to create a Bach such that the CVS is not needed to indicate the corresponding system user later, and the PubCVS behind melissa is the system user, the user exists on the local system. The format of the two users who want to use commands is as follows:
CVS Passwd -a Bach
CVS Passwd -r Pubcvs -a Melissa
Create a simple passwd initialization file on the server when you build, add a line
Cvsadmin:
In this way, a cvsadmin is given this empty password user (such a user in the local system, you can do not add it), and then the client is modified and the future user increases. Note: First modify this password first before you have other yours, to prevent others from being destroyed.
After the server is established in the server, you don't have to modify it again. When you pass your client, you will automatically perform this file update. This file is managing all users in the CVSNT system, so it is necessary to pay special attention, do not understand this file format, do not want to modify, do not try to modify it at the client!
1.3 Admin File This file is a file for the administrator list specified by the CVSNT. CVSNT will determine if a user is an administrator based on the content in this file. The content of this file is very simple, it is a list of users. Similar to
User1
User2
User3
These representatives USER1, USER2, and User3 are administrators, of course, these users must exist to log in to the system correctly to perform management.
This file is not available by default, however, you can add it on the client, add this file in your client, then add the file, this file can be uploaded to the server, but this time has not taken effect, please Modify the checkoutList this file, join the ADMIN line, checkoutList can also modify it again on the client, this time admin can be automatically automatically build.
CheckoutList is a list of maintained files, which can be placed in the system automatic build user-defined system file list, pay attention: it is useless to Passwd! ! 1.4 Group file This file is a group that defines the system. We can place the same nature user into a group, then give the group to assapore to the user, so that a group of users will have the same authority. . The content of Group is as follows:
Group1: User1 User2 User3
Group2: me you he
Group3: Tom Honey
It can be seen above, the content of this document is also quite simple, first is the name of the group and the colon, then the username, multiple usernames are split by spaces.
Group files can be created and modified on the client, do not modify the checkoutList file, the system automatically build this file and takes effect.
As a particular member of the group, it can also assign a specific permissions, and the permissions are divided into two types C, W, R, R and N, and the negative authority is high priority.
Ok, there have been a few important documents and modifications involved in this scheme. Here, it is emphasized that the passwd can only be established and modified by the server side, and cannot be operated on the client!
Now, according to the content described above, you can start your operation. Here, the modification order is given. When the library has just established, use the local administrator user on one server to check out the CVSROOT module.
1. Now the server side plus the Passwd file to give an initial user, such as cvsadmin:
2. Add admin to add cvsadmin to the Admin file, and submit it to the library.
3. In the modification of the checkoutList file, add admin to automatically automatically build.
4, finally modify the systemAuth = no of the config file, to confirm if you are submitted, if this file is submitted, the CVSNT verification mode begins to take effect!
5, good, now please modify your parameters to re-login. Because your system has switched the working mode, your current user has been invalid.
Completed the above steps, the entire server will work in CVSNT verification mode. The group file can be added at any time you need.
In the above article, there is a point of addition to the user's management scheme of CVSNT. In the following operation, it is for the client's use of WinCVS (increasing passwd) files, in fact, in my practice CONFIG, PASSWD, Admin, CheckoutList, start modification (initialization) of these files can be completed after the new library is created, and then the administrator of the corresponding library will be performed.
In my article, this article is based on another article. You can search for the operation of CVSNT and WinCVS on the Internet. However, I think that something is a bit chaotic, so I will have a little modification. I always want to post it here, but there are too many pictures, :(
Welcome to my blog http://scottding.blogger.cn
