Hi there! This post will be pretty straightforward and will cover Windows, Mac, and Linux, so if you don’t know how to do it already, read on.
Windows
Windows 10, 8.1, and 7: Git for Windows. The easiest way to install Git and the SSH client on Windows 8.1 and Windows 7 is Git for Windows. It provides a Bash emulation (Git Bash) used for running Git from the command line and the ssh-keygen command that is useful to create SSH keys as you’ll learn below. RSA keys and OpenSSH from versions 6.5 to 7.8. Before OpenSSH 7.8, the default public key fingerprint for RSA keys was based on MD5, and is therefore insecure. If your version of OpenSSH lies between version 6.5 to version 7.8 (inclusive), run ssh-keygen with the -o option to save your private SSH keys in the more secure OpenSSH format.
This developer discussion might be relevant. Maybe you could try an earlier version, as even 1.7.6 was released after those changes were added. Version 1.7.4 would be earlier. If that version works, you should report a bug on the msysGit mailing list.And if you. With both Tectia SSH and OpenSSH servers, access to an account is granted by adding the public key to a /.ssh/authorizedkeys file on the server. To install the public key, Log into the server, edit the authorizedkeys file with your favorite editor, and cut-and-paste the public key output by the above command to the authorizedkeys file. Create and add your SSH key pair. It is best practice to use Git over SSH instead of Git over HTTP. In order to use SSH, you will need to: Create an SSH key pair; Add your SSH public key to GitLab. Creating your SSH key pair. Go to your command line. Follow the instructions to generate your SSH key pair. Generating Your SSH Public Key Many Git servers authenticate using SSH public keys. In order to provide a public key, each user in your system must generate one if they don’t already have one.
Just follow these 5 steps:
Go to this address, and download Git for Windows, after the download install it with default settings
Open Git Bash that you just installed (Start->All Programs->Git->Git Bash)
Type in the following: ssh-keygen -t rsa (when prompted, enter password, key name can stay the same)
Open file your_home_directory/.ssh/id_rsa.pub with your favorite text editor, and copy contents to your Git repository’s keys field (GitHub, beanstalk, or any other repository provider), under your account.
Be sure that you don’t copy any whitespace while copying public key’s content (id_rsa.pub)
Note: your_home_directory is either C:Usersyour_username (on Windows Vista / 7 / 8 / 10), or C:Documents and Settingsyour_username (on Windows XP)
Mac
Follow these 5 steps:
Start the terminal
Navigate to your home directory by typing: cd ~/
Execute the following command: ssh-keygen -t rsa (when prompted, enter password, key name can stay the same)
Open the file you’ve just created ~/.ssh/id_rsa.pub with your favorite text editor, and copy contents to your Git repository’s keys field (GitHub, beanstalk, or any other repository provider), under your account.
Be sure that you don’t copy any whitespace while copying public key’s content (id_rsa.pub)
Linux (Ubuntu)
Follow these 5 steps:
Open console
cd ~
ssh-keygen -t rsa (when prompted, enter password, key name can stay the same)
open file /home/your_username/.ssh/id_rsa.pub with your favorite text editor, and copy contents to your Git repository’s keys field (GitHub, beanstalk, or any other repository provider), under your account.
Be sure that you don’t copy any whitespace while copying public key’s content (id_rsa.pub)
Generate Ssh Key File In Windows
Additional info
Generate Ssh Key Windows Github
When you create private/public SSH keys on your machine (that’s what you did in the above steps), it’s not enough. You need to give your public key to the repository in order to pair the Git server with your local machine (that’d be steps 4. and 5. above).
Most of the popular repositories will give you web interface access to the application, and here’s how it looks like on Github: After this step, you’re ready to start using Git.
Conclusion
I hope this wasn’t too complicated to follow, and also I hope it was helpful to someone!