Last updated 2 November 2018.
Apr 02, 2019 Installation of SSH Keys on Linux - A Step-By-Step Guide. Outlined below is a step-by-step guide detailing the process of installing SSH Keys on a Linux server: Step One: Creation of the RSA Key Pair. The first step in the installation process is to create the key pair on the client machine, which would, more often than not, be your own system.
Before generating any key check the .ssh folder in user directory for previously generated keys. First open a terminal on your machine. On Ubuntu Linux you can use the keyboard shortcut ctrl+alt+t. Then enter the following (without the '$' sign):
You may want to use your existing SSH key pairs to make your life a little simpler. For example, you may already have shared your public SSH key to other systems and if you generate new ones you will have to update existing trust relationships with your new public key.
However, you may also just want to use this opportunity to generate fresh key pairs and roll those out to improve security, or you may be worried that your current private key has been compromised. /destiny-2-license-key-generator.html.
If you want to replace your existing keys (id_rsa, id_rsa.pub files), you should backup those keys, otherwise skip the step below and jump to Generate new key pairs.
From your terminal enter:
You should see:
Press 'Enter' here to accept the default.
DO NOT just press enter to leave the passphrase empty. It is important that you use a strong passphrase for this key. If you do not use a passphrase, anyone who gets access to your key (such as if your laptop were stolen or your computer got a virus) could easily commit code as you -- people who trust you could then run malicious code, compromising their servers.
At the prompt, type:
You should see something like:
In Linux you can use a tool called xclip for copying the contents of your public key quickly. The command for this is:
To test your key, clone an actual project from drupal.org. You can use the example below or locate the clone command for a project you actually need. The Git project clone will be saved in the directory you are located in.
You should see:
Type 'yes' at the prompt and press 'Enter'.
If this is the first time you are accessing after setting up your SSH at drupal.org. You will be requested for the git password, which is the same as your drupal.org password.
Next you'll see something like:
If you're just testing, then finish by cleaning up:
Could the ssh key be tested using a similar method to Generating SSH Keys - GitHub - Test everything out instead cloning a repository?
Where I should write these 2 commands from the beginning? On my office wall?! I miss this information.
I have updated the page:
Open shell/command line in your local machine. There's a shortcut CTRL+ALT+T available for Ubuntu users.
It does seem to make sense to have this placed within the documentation; however, it seemed out of context at the very top of this page. So I have moved it into the first paragraph, and reorganized the words to help the new linux user.
I received an email two weeks ago from Drupal.org regarding git access to my projects and sandboxes.
Two problems with this documentation:
1) I already use SSH keys to log on to other systems on my network. So you want me to back up and generate new keys?
That's a FAIL. I'm not going to do that.
Instead I copied my existing public key to git.drupal.org using 'xclip' as you suggested. That worked on drupal.org after I installed xclip. And the LAN still works as before.
2) I use a different port number (instead of the default 22) for SSH . So I had to modify the suggested git clone command as follows:
git clone ssh://git@git.drupal.org:22/project/[projectname].git
It worked for me. Your mileage may vary. With Drupal it usually does.