background:Recently used BitBucket as the remote repository Management code, because each time the push code needs to enter the account password, they provide the SSH protocol so that the push code does not need to enter the account password.
How to use:A machine only need to generate a private key in the ~/.SSH to a public key, and then upload your public key to BitBucket, if someone else wants to upload the code, then upload his public key to BitBucket, it should be. In addition, if there is a dialog box that asks for the password for SSH id_rsa, enter the blank directly.
generate SSH Key:1, terminal input: Ssh-keygen2, ask you to create the key to save where, directly enter, the default will be saved in~/.ssh/; 3, query input passphrase, or direct enter;4, after the success of the use of Vim to view the id_rsa.pub, copy the contents of the Paste to Github/bitbucket;
ScienceSSH forSecure Shellis established by the Network Working group of the IETF, and SSH is a security protocol based on the application layer and the transport layer. SSH is now more reliable and is designed forTelnetprotocols that provide security for sessions and other network services. The use of SSH protocol can effectively prevent the information leakage in the remote management process. SSH was originally a program on a UNIX system, and later expanded quickly to other operating platforms. SSH can compensate for vulnerabilities in the network when it is used correctly. The SSH client is available on a variety of platforms. Almost all UNIX platforms-includingHP-UX,Linux,Aix,Solaris,Digital Unix,Irix, and other platforms, you can run SSH. from the client side, SSH provides two levels of security validation. First level (password-based security authentication)As long as you know your account number and password, you can log on to the remote host. All transmitted data will be encrypted, but there is no guarantee that the server you are connecting to is the one you want to connect to. There may be other servers impersonating a real server, which is an attack by the "middleman".Second level (key-based security verification)You need to rely on the key, which means you have to create a pair of keys for yourself and place the public key on the server you need to access. If you are connecting to an SSH server, the client software makes a request to the server requesting security verification with your key. After the server receives the request, look for your public key in your home directory on the server and compare it to the public key you sent. If the two keys are consistent, the server encrypts the "Challenge" (challenge) with a public key and sends it to the client software. After the client software receives a "challenge", it can use your private key to decrypt it and send it to the server. In this way, you must know the password of your secret key. However, the second level does not require a password to be sent over the network compared to the first level. The second level not only encrypts all transmitted data, but the "man in the middle" approach is also impossible (because he does not have your private key). However, the entire login process may take up to 10 seconds.
We are using the second level of security.
The ssh inside git
