Shulou(Shulou.com)06/01 Report--

This article mainly introduces the relevant knowledge of how to build a private Git server in Centos. The content is detailed and easy to understand, easy to operate, and has a certain reference value. I believe you will gain something after reading this article on how to build a private Git server in Centos. Let's take a look.

GitHub is a remote repository that hosts open source code for free. But for some commercial companies that see source code such as life, they do not want to release the source code and are reluctant to pay GitHub protection fees, so they can only build their own Git server to use as a private warehouse.

1. First, you need to install Git. You can install it online using the yum source:

[root@localhost Desktop] # yum install-y git

2. Create a git user to run the git service

Adduser git

3. Initialize the git repository:

Here we choose / data/git/learngit.git as our git repository

[root@localhost git] # git init-- bare learngit.gitInitialized empty Git repository in / data/git/learngit.git/

Executing the above command creates a naked warehouse, which does not have a workspace, because the Git warehouse on the server is purely for sharing, so users are not allowed to log in directly to the server to change the workspace, and the Git warehouse on the server usually ends with .git. Then, change owner to git:

[root@localhost git] # chown git:git learngit.git

4. Here, the Git server has been built almost.

Let's take a look at the remote warehouse on the client side clone.

Zhu@XXX / E/testgit/8.34$ git clone git@192.168.8.34:/data/git/learngit.gitCloning into 'learngit'...The authenticity of host' 192.168.34 (192.168.34) 'can't be established.RSA key fingerprint is 2b:55:45:e7:4c:29:cc:05:33:78:03:bd:a8:cd:08:9d.Are you sure you want to continue connecting (yes/no)? YesWarning: Permanently added '192.168.8.34' (RSA) to the list of known hosts.git@192.168.8.34's password:

Here are two things to note: first, when you connect to GitHub for the first time using Git's clone or push command, you will get a warning:

The authenticity of host 'github.com (xx.xx.xx.xx)' can't be established.RSA key fingerprint is xx.xx.xx.xx.xx.Are you sure you want to continue connecting (yes/no)?

This is because Git uses SSH connection, and when SSH connection verifies the Key of GitHub server for the first time, you need to confirm whether the fingerprint information of GitHub's Key really comes from GitHub server, enter yes and enter enter. Git will output a warning telling you that GitHub's Key has been added to a trust list on this machine:

Warning: Permanently added 'github.com' (RSA) to the list of known hosts.

This warning will only appear once, and there will be no warnings for subsequent actions. If you are really worried about someone posing as a GitHub server, you can check whether the fingerprint information of GitHub's RSA Key is consistent with that given by the SSH connection before entering yes. Second, you are prompted to enter a password to clone, of course, if you know the password, you can type the password to clone, but the more common way is to use the public key of SSH to complete the authentication.

5. Create SSH Key

First of all, under the user's home directory, see if there is a .ssh directory, and if so, see if there are id_rsa and id_rsa.pub files in this directory. If you already have one, you can skip to the next step.

If not, open Shell (open Git Bash under Windows) and create a SSH Key:

$ssh-keygen-t rsa-C "youremail@example.com"

You need to change your email address to your own email address, and then enter all the way, using the default value, and since this Key is not used for military purposes, there is no need to set a password. If all goes well, you can find the .ssh directory in the user's home directory, which contains two files, id_rsa and id_rsa.pub, which are the key pairs of SSH Key. Id_rsa is the private key and cannot be leaked out. Id_rsa.pub is the public key and you can safely tell anyone.

6. Open the RSA authentication on the Git server

Then you can add your public key to the Git server to verify your information.

On the Git server, you first need to turn on the RSA authentication in / etc/ssh/sshd_config, that is:

1.RSAAuthentication yes2.PubkeyAuthentication yes3.AuthorizedKeysFile .ssh / authorized_keys

Here we can see that the public key is stored in the .ssh / authorized_keys file. So we create the .ssh directory under / home/git, then create the authorized_keys file, and import the public key we just generated. Then when you clone again, or later when you push, you don't need to enter the password:

Zhu@XXX/E/testgit/8.34$ git clone git@192.168.8.34:/data/git/learngit.gitCloning into 'learngit'...warning: You appear to have cloned an empty repository.Checking connectivity... Done.

7. Disable shell login for git users

For security reasons, the git user created in step 2 is not allowed to log in to shell, which can be done by editing the / etc/passwd file. Find a line similar to the following:

Git:x:1001:1001:,:/home/git:/bin/bash

The last colon is changed to:

Git:x:1001:1001:,:/home/git:/usr/bin/git-shell

In this way, git users can normally use git through ssh, but cannot log in to shell because the git-shell we specified for git users automatically logs out each time they log in.

This is the end of the article on "how to build a private Git server in Centos". Thank you for reading! I believe you all have a certain understanding of "how to build a private Git server in Centos". If you want to learn more, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.