Git on Linux installation is not much said, reference to the following article can be successfully completed, mainly rely on the library.
Install git
Http://progit.org/book/zh/ch1-4.html
Git trouble in user management and management, the following three solutions:
1. Providing SSH connectivity is the only option if you need everyone on the team to have write access to the warehouse, and you can't create an account for everyone on the server. We assume that the server used to share the warehouse has SSH service installed, and that you access the server through it. 2.3. There are several ways to have access to everyone in the team. The first option is to create an account for everyone, straightforward but cumbersome. It is not fun to run the AddUser repeatedly and set the temporary password for everyone. 4.5. The second option is to create a git account on the host and have each person who needs write permission send an SSH public key and then add it to the ~/.ssh/authorized_keys file of the Git account. In this way, everyone will access the host via Git account. This does not affect the data submitted at all--the identity of the access host does not affect the record of the commit. 6.7. Another option is to have the SSH server authorize through an LDAP service, or other centrally authorized mechanisms that have already been set up. As long as everyone has access to the shell of the host, any available SSH authorization mechanism can achieve the same effect. If you need everyone on your team to have write access to the warehouse, and you can't create an account for everyone on the server, then providing SSH connectivity is the only option. We assume that the server used to share the warehouse has the SSH service installed, and that you access the server through it. There are several ways to make everyone in the team have access. The first option is to create an account for everyone, straightforward but cumbersome. It's not fun to run adduser repeatedly and set temporary passwords for everyone. The second option is to set up a git account on the host, so that everyone who needs write permission sends a SSH public key and then joins the git Account ~/.ssh/authorized_keys documents. In this way, everyone will access the host via the git account. This does not affect the data submitted at all--the identity of the access host does not affect the record of the commit. Another option is to have the SSH server authorize it through a LDAP service, or some other set of centralized authorization mechanisms. As long as everyone canAccess to the host shell access, any available SSH authorization mechanism can achieve the same effect
Providing SSH connectivity is the only option if you need everyone on the team to have write access to the warehouse, and you can't create an account for everyone on the server. We assume that the server used to share the warehouse has SSH service installed, and that you access the server through it.
There are several ways to make everyone in the team have access. The first option is to create an account for everyone, straightforward but cumbersome. It is not fun to run the AddUser repeatedly and set the temporary password for everyone. The
second option is to create a git account on the host and have each person who needs write permission send an SSH public key and then add it to the GIT account's ~/.ssh/authorized_keys file. In this way, everyone will access the host via Git account. This does not affect the data submitted at all--the identity of the access host does not affect the record of the commit.
Another option is to have the SSH server authorize it through an LDAP service, or some other set of centralized authorization mechanisms. As long as everyone has access to the shell of the host, any available SSH authorization mechanism can achieve the same effect
For the convenience of the second option, this approach uses SSH public key authentication.
1. Generate Public key
Java code 1.SSH-KEYGEN-C "Your email address"-T-RSA back to the end, the middle can not need any settings, the command will generate a pair of asymmetric public/private keys, the default they are stored in:
xp/2003 User: C:/Documents and settings/landing name/.ssh
Vista users: c:/users/Landing name/.ssh
Under the. SSH folder, the key is placed in the Id_rsa file without regard to it;
2. Add the public key to the Authorized_keys file of the Git user on the Linux server.
can refer to: http://github.com/git-on-windows/rookies
Git user's establishment and setting reference: http://progit.org/book/zh/ch4-4.html
Note that the warehouse on git has write access to git users and will need to open RSA authentication in/etc/ssh/sshd_config, namely:
Java code 1.RSAAuthentication Yes 2.PubkeyAuthentication Yes 3.AuthorizedKeysFile. Ssh/authorized_keys
Rsaauthentication Yes
pubkeyauthentication Yes
authorizedkeysfile . Ssh/authorized_keys
In addition, when I connect with git user on Ubuntu, the agent admitted failure to sign using the key error, check the need to start ssh-agent, and then add Id_rsa to Ssh-agent, You can connect it again.
Reference: http://www.jiangmiao.org/blog/559.html
