kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Improvements to setting up ssh

Browse source
This commit is contained in:
Sean Packham 2016-09-28 14:45:28 +01:00 committed by Achilleas Pipinellis
parent 911c1601f8
commit 1038d37671
1 changed files with 91 additions and 59 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

150
doc/ssh/README.md
View file

@ -1,12 +1,21 @@
# SSH
## SSH keys
Git is a distributed version control system, which means you can work locally
but you can also share or "push" your changes to other servers.
Before you can push your changes to a GitLab server
you need a secure communication channel for sharing information.
GitLab uses Public-key or asymmetric cryptography
which "encrypts" a communication channel by locking it with your "private key"
and allows trusted parties to unlock it with your "public key".
If someone does not have your public key they cannot access the unencrypted message.
An SSH key allows you to establish a secure connection between your
computer and GitLab. Before generating an SSH key in your shell, check if your system
already has one by running the following command:
## Locating an existing SSH key pair
**Windows Command Line:**
Before generating a new SSH key check if your system already has one
at the default location by opening a shell, or Command Prompt on Windows,
and running the following command:
**Windows Command Prompt:**
```bash
type %userprofile%\.ssh\id_rsa.pub
```
@ -15,40 +24,52 @@ type %userprofile%\.ssh\id_rsa.pub
cat ~/.ssh/id_rsa.pub
```
If you see a long string starting with `ssh-rsa`, you can skip the `ssh-keygen` step.
If you see a string starting with `ssh-rsa` you already have an SSH key pair
and you can skip the next step **Generating a new SSH key pair**
and continue onto **Copying your public SSH key to the clipboard**.
If you don't see the string or would like to generate a SSH key pair with a custom name
continue onto the next step.
## Generating a new SSH key pair
To generate a new SSH key, use the following command:
**GNU/Linux/Mac/PowerShell:**
```bash
ssh-keygen -t rsa -C "$your_email"
```
This command will prompt you for a location and filename to store the key
pair and for a password. When prompted for the location and filename, just
press enter to use the default. If you use a different name, the key will not
be used automatically.
Note: It is a best practice to use a password for an SSH key, but it is not
required and you can skip creating a password by pressing enter.
**Windows:**
On Windows you will need to download
[PuttyGen](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
and follow this documentation
[article](https://the.earth.li/~sgtatham/putty/0.67/htmldoc/Chapter8.html#pubkey-puttygen)
to generate a SSH key pair.
If you want to change the password of your key later, you can use the following
command: `ssh-keygen -p <keyname>`
### Provide a file path
Use the command below to show your public key:
You will be prompted to input a file path to save your key pair to.
**Windows Command Line:**
```bash
type %userprofile%\.ssh\id_rsa.pub
```
**GNU/Linux/Mac/PowerShell:**
```bash
cat ~/.ssh/id_rsa.pub
```
If you don't already have an SSH key pair use the suggested path by pressing enter.
Using the suggested path will allow your SSH client
to automatically use the key pair with no additional configuration.
Copy-paste the key to the 'My SSH Keys' section under the 'SSH' tab in your
user profile. Please copy the complete key starting with `ssh-rsa` and ending
with your username and host.
If you already have a key pair with the suggested file path you will need to input a new file path
and declare what host this key pair will be used for in your `.ssh/config` file,
see **Working with non-default SSH key pair paths** for more information.
To copy your public key to the clipboard, use the code below. Depending on your
OS you'll need to use a different command:
### Provide a password
Once you have input a file path you will be prompted to input a password to secure your SSH key pair.
Note: It is a best practice to use a password for an SSH key pair,
but it is not required and you can skip creating a password by pressing enter.
If you want to change the password of your key, you can use the following command:
`ssh-keygen -p <keyname>`
## Copying your public SSH key to the clipboard
To copy your public key to the clipboard, use the appropriate code for you operating system below:
**Windows Command Line:**
```bash
@ -70,6 +91,48 @@ pbcopy < ~/.ssh/id_rsa.pub
xclip -sel clip < ~/.ssh/id_rsa.pub
```
## Adding your public SSH key to GitLab
Navigate to the 'SSH Keys' tab in you 'Profile Settings'.
Paste your key in the 'Key' section and give it a relevant 'Title'.
Use an identifiable title like 'Work Laptop - Windows 7' or 'Home MacBook Pro 15'.
If you manually copied your public SSH key make sure you copied the entire key
starting with `ssh-rsa` and ending with your email.
## Working with non-default SSH key pair paths
If you used a non-default file path for your GitLab SSH key pair,
you must configure your SSH client to find your GitLab SSH private key
for connections to your GitLab server (perhaps gitlab.com).
For OpenSSH clients this is configured in the `~/.ssh/config` file.
Below are two example host configurations using their own key:
```
# GitLab.com server
Host gitlab.com
RSAAuthentication yes
IdentityFile ~/folder1/private-key-filename
User mygitlabusername
# Private GitLab server
Host gitlab.company.com
RSAAuthentication yes
IdentityFile ~/folder2/private-key-filename
```
Note in the gitlab.com example above a username was specified
to override the default chosen by OpenSSH (your local username).
This is only required if your local and remote usernames differ.
Due to the wide variety of SSH clients and their very large number of configuration options,
further explanation of these topics is beyond the scope of this document.
Public SSH keys need to be unique, as they will bind to your account.
Your SSH key is the only identifier you'll have when pushing code via SSH.
That's why it needs to uniquely map to a single user.
## Deploy keys
Deploy keys allow read-only access to multiple projects with a single SSH
@ -99,34 +162,3 @@ Deploy keys can be shared between projects, you just need to add them to each pr
### Eclipse
How to add your ssh key to Eclipse: https://wiki.eclipse.org/EGit/User_Guide#Eclipse_SSH_Configuration
## Tip: Non-default OpenSSH key file names or locations
If, for whatever reason, you decide to specify a non-default location and filename for your GitLab SSH key pair, you must configure your SSH client to find your GitLab SSH private key for connections to your GitLab server (perhaps gitlab.com). For OpenSSH clients, this is handled in the `~/.ssh/config` file with a stanza similar to the following:
```
#
# Main gitlab.com server
#
Host gitlab.com
RSAAuthentication yes
IdentityFile ~/my-ssh-key-directory/my-gitlab-private-key-filename
User mygitlabusername
```
Another example
```
#
# Our company's internal GitLab server
#
Host my-gitlab.company.com
RSAAuthentication yes
IdentityFile ~/my-ssh-key-directory/company-com-private-key-filename
```
Note in the gitlab.com example above a username was specified to override the default chosen by OpenSSH (your local username). This is only required if your local and remote usernames differ.
Due to the wide variety of SSH clients and their very large number of configuration options, further explanation of these topics is beyond the scope of this document.
Public SSH keys need to be unique, as they will bind to your account. Your SSH key is the only identifier you'll
have when pushing code via SSH. That's why it needs to uniquely map to a single user.