Generate A Ssh Key Github

  

SSH keys come in pairs, a public key that gets shared with services like GitHub, and a private key that is stored only on your computer. If the keys match, you're granted access. The cryptography behind SSH keys ensures that no one can reverse engineer your private key from the public one. Generating an SSH key pair. Verifying Added SSH Key in GitHub Account. Now that the SSH key has generated and added in our GitHub account, it is time we check the key with our GitHub account with the help of ssh and GitBash. Go to the Git Bash and type the following command: ssh -T email protected. Nov 05, 2019 The concept is we create a public/private key pair; put the public key to the remote server, and keep the private key on your local machine. The server can authenticate the client if the client has the corresponding private key. First we need to generate key pair. Type this command on Git Bash: ssh-keygen -t rsa.

  1. Generate A Ssh Key Github Pdf
  2. Adding Ssh Key To Github
  3. Creating A New Ssh Key Github
  4. Generate A New Ssh Key Github
  5. Generate Ssh Public Key Github

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2020-01-22. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise.For help with the upgrade, contact GitHub Enterprise support.

After you've checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.

In this article

If you don't already have an SSH key, you must generate a new SSH key. If you're unsure whether you already have an SSH key, check for existing keys.

If you don't want to reenter your passphrase every time you use your SSH key, you can add your key to the SSH agent, which manages your SSH keys and remembers your passphrase.

Generating a new SSH key

  1. Open TerminalTerminalGit Bash.

  2. Paste the text below, substituting in your GitHub Enterprise email address.

    This creates a new ssh key, using the provided email as a label.

  3. When you're prompted to 'Enter a file in which to save the key,' press Enter. This accepts the default file location.

  4. At the prompt, type a secure passphrase. For more information, see 'Working with SSH key passphrases'.

Adding your SSH key to the ssh-agent

Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. When adding your SSH key to the agent, use the default macOS ssh-add command, and not an application installed by macports, homebrew, or some other external source.

  1. Start the ssh-agent in the background.

  2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your ~/.ssh/config file to automatically load keys into the ssh-agent and store passphrases in your keychain.

  3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

    Note: The -K option is Apple's standard version of ssh-add, which stores the passphrase in your keychain for you when you add an ssh key to the ssh-agent.

    If you don't have Apple's standard version installed, you may receive an error. For more information on resolving this error, see 'Error: ssh-add: illegal option -- K.'

  4. Add the SSH key to your GitHub account.

If you have GitHub Desktop installed, you can use it to clone repositories and not deal with SSH keys. It also comes with the Git Bash tool, which is the preferred way of running git commands on Windows.

  1. Ensure the ssh-agent is running:

    • If you are using the Git Shell that's installed with GitHub Desktop, the ssh-agent should be running.

    • If you are using another terminal prompt, such as Git for Windows, you can use the 'Auto-launching the ssh-agent' instructions in 'Working with SSH key passphrases', or start it manually:

  2. Add your SSH private key to the ssh-agent. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

  3. Add the SSH key to your GitHub account.

  1. Start the ssh-agent in the background.

  2. Add your SSH private key to the ssh-agent. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

  3. Add the SSH key to your GitHub account.

Further reading

  • 'About SSH'
  • 'Working with SSH key passphrases'

Today’s post is for developers. If you use the Git version control system with a service such as GitHub, GitLab or Bitbucket to host and manage your projects source codes, you know that by default Git connects to remotes using the HTTPS protocol, which requires you to enter username and password every time you run a command such as git pull or git push.

Using the SSH protocol, you can connect and authenticate to servers to use their services. The three mentioned services allow Git to connect via SSH instead of HTTPS. Connecting with public key encryption dispenses typing username and password for every Git command.

You are going to see in this post how to use GitHub, GitLab and Bitbucket with SSH.

Make sure an SSH client in installed

In order to connect using the SSH protocol, an SSH client must be installed on your system. If you use openSUSE, it should be already installed by default.

Just to make sure, open the terminal and run:

That command should output the version number of the SSH client being used:

In case the system informs that the ssh command was not found, you can install the OpenSSH client running:

Check for existing SSH keys

To connect using the SSH protocol, you need an SSH key pair (one private and the other public). If you have never used SSH, you can safely skip this topic and move on to the next. If you have ever used SSH (for instance, to remotely access a server), probably you already have an SSH key pair, in which case you don’t need to generate a new key pair.

To see if existing SSH keys are present, run:

That command should list the contents of the ~/.ssh folder, in which the SSH client stores its configuration files:

If you receive an error that there is no ~/.ssh directory or there are no files in it, don’t worry: it means you haven’t created an SSH key pair yet. If that is the case, proceed to the next topic.

By default, public SSH keys are named:

  • id_dsa.pub;
  • id_ecdsa.pub;
  • id_ed25519.pub; or
  • id_rsa.pub.

Inside my ~/.ssh folder, I have an SSH key pair (id_rsa.pub is the public key and id_rsa is the private key) created a year ago (Jul 18 2018).

For security reasons, it is recommended that you generate a new SSH key pair at least once a year. If you already have an SSH key pair that was created more than a year ago, it is recommended that you proceed to the next topic.

If you already have an SSH key pair and want to reuse it, you can skip the next topic.

Generate a new SSH key pair

To generate a new SSH key pair, run the following command (replace your_email@example.com with your email address):

It asks you where to save the private key (id_rsa).

Press Enter to accept the default location.

If you already have a private key, it asks whether it should overwrite:

If that happens, type y and press Enter.

Then, enter and re-enter a passphrase (think of it as a kind of password):

The SSH key pair is created in ~/.ssh.

The whole interaction should look similar to the following:

Add the private SSH key to the ssh-agent

If you don’t want to type your passphrase each time you use your SSH keys, you need to add it to the ssh-agent, which is a program that runs in background while you are logged in to the system and stores your keys in memory.

To start the ssh-agent in background, run the following:

That command outputs the ssh-agentprocess identifier:

Then, add your SSH private key to the ssh-agent:

Type your passphrase and press Enter:

The command confirms that the private SSH key has been added to the ssh-agent:

Add the public SSH key to your account

Once you have an SSH key and have added it to the ssh-agent, you can set up connecting via SSH. Let’s see how to do that for each of the three servers: GitHub, GitLab and Bitbucket.

In all the three cases, the process is similar. Start by copying your public SSH key (~/.ssh/id_rsa.pub) file contents to the clipboard using the xclip command:

xclip is a command line utility that allows access to the graphical interface clipboard from the terminal. If it is not installed, you can install it running:

GitHub

Using a browser, go to the GitHub home page at github.com and sign in to your account.

In the upper-right corner of the page, click your profile photo, then click Settings:

In the user settings sidebar, click SSH and GPG keys. Then click New SSH key.

Fill in the Title field with a descriptive label for the new key (for example, the name of your computer) and paste your public key into the Key field. Finally, click Add SSH key:

Now the key appears in the list of SSH keys associated with your account:

GitLab

Using a browser, go to the GitLab home page at gitlab.com and sign in to your account.

In the upper-right corner of the page, click your profile photo, then click Settings:

In the User Settings sidebar, click SSH Keys.

Paste your public key in the Key field. Fill in the Title field with a descriptive label for the new key (for example, the name of your computer). Finally, click Add key:

Now the key appears in the list of SSH keys associated with your account:

Bitbucket

Using a browser, go to the Bitbucket home page at bitbucket.org and log in to your account.

In the lower-left corner of the page, click your profile photo, then click Bitbucket settings:

In the Settings sidebar, in the Security section, click SSH keys. Then, click Add key.

Fill in the Label field with a descriptive label for the new key (for example, the name of your computer) and paste your public key into the Key field. Finally, click Add key:

Now the key appears in the list of SSH keys associated with your account:

Test connecting via SSH

GitHub, GitLab and Bitbucket allow you to test whether SSH connection has been set up correctly before actually using it with Git.

GitHub

After you’ve added your SSH key to your GitHub account, open the terminal and run:

That command attempts an SSH remote access to GitHub.

If that is the first time you connect to GitHub via SSH, the SSH client asks you if it can trust the public key of the GitHub server:

Generate A Ssh Key Github Pdf

Type yes and press Enter. The SSH client adds GitHub to the list of trusted hosts:

Once added to the list of known hosts, you won’t be asked about GitHub’s public key again.

As this remote access via SSH is provided by GitHub just for testing, not for actual use, the server informs that you have successfully authenticated and terminates the connection:

If you completed the test successfully, now you can use SSH with GitHub.

The whole interaction should look similar to the following:

GitLab

If you have added your SSH key to your GitLab account, the test is very similar:

If you completed the test successfully, now you can use SSH with GitLab.

Bitbucket

If you have added your SSH key to your Bitbucket account, the test is very similar:

If you completed the test successfully, now you can use SSH with Bitbucket.

Clone a repository using SSH

Now that we’ve got our SSH keys set up, let’s see how to clone a Git repository using SSH instead of HTTPS.

GitHub

At GitHub, go to a project’s repository, click Clone or download and copy the URL to clone the repository using SSH:

The URL of a GitHub repository looks like:

Open the terminal and run the git clone command passing the copied URL as argument.

Tip: to paste into the terminal, use Ctrl + Shift + V.

Note that now Git clones the repository without asking for a password:

GitLab

At GitLab, go to a project’s repository, click Clone and copy the URL to clone the repository using SSH:

The URL of a GitLab repository looks like:

Open the terminal and run the git clone command passing the copied URL as argument:

Note that now Git clones the repository without asking for a password.

Bitbucket

At Bitbucket, go to a project’s repository, click Clone and copy the command to clone the repository using SSH:

Adding Ssh Key To Github

Note that, differently from GitHub and GitLab that present the URL, Bitbucket presents the entire git clone command, including the URL.

The URL of a Bitbucket repository looks like:

Open the terminal, paste and run the command you copied from Bitbucket:

Note that now Git clones the repository without asking for a password.

Creating A New Ssh Key Github

Reconfigure existing repositories to use SSH

The repositories we clone from now on using SSH will continue to use SSH for future Git commands such as git pull and git push. But existing local repositories, previously cloned with HTTPS, will continue to use HTTPS, unless we set them up to use SSH.

To do that, open the terminal and change the current directory to a local repository.

List the existing remote repositories and their URLs with:

That command should output something like:

Change your remote repository’s URL with:

Run git remote -v once more to verify that the remote repository’s URL has changed:

Great. That done, Git will use SSH, instead of HTTPS, to synchronize that local repository with its remote equivalent.

References

Generate A New Ssh Key Github

I hope those tips can be useful to you as they have been to me since I started using Git. If you have any questions or trouble, don’t hesitate to comment! See you!

Generate Ssh Public Key Github

And always remember: have a lot of fun…