-
Notifications
You must be signed in to change notification settings - Fork 25
/
Copy pathSSH.qmd
147 lines (102 loc) · 5.76 KB
/
SSH.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
---
title: "Secure the connection between your computer and GitHub"
format: html
---
When working with a GitHub repository, you'll often need to identify yourself to GitHub using your username and password. There are several ways to secure this connection further. Establishing a secure connection is mandatory since August 2021.
Today we will use **SSH Keys** to secure your identification to GitHub as this is a common way to secure connections, which you may encounter again in other contexts in the future.
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 procedure below only need to be executed once per GitHub account and for each computer you will use to connect to GitHub.
## Checking for existing SSH key pair
The first step in using SSH authorization with GitHub is to generate your own key pair.
However, you might already have an SSH key pair on your machine. You can check to see if one exists by moving to your `.ssh` directory and listing the contents.
On windows, open **Git Bash** (start menu -> Git Bash). On MacOS, open
the **Terminal** app. On Linux, open your distribution's (or any
other) terminal emulator. Enter the following commands one after the
other (hitting ENTER after each command).
```bash
ls ~/.ssh
```
The `ls` command lists the content of a directory, here `~/.ssh`. Check the directory listing to see if you already have a public SSH key. By default, the filenames of the public keys are one of the following:
```bash
id_rsa.pub
id_ecdsa.pub
id_ed25519.pub
```
If you do have one, you can skip the section that generate a SSH key pair, and go to the section 'Adding a new SSH key to your GitHub account'.
**If you don't have an existing public and private key pair (which is to be expected!), or if you receive an error that ~/.ssh doesn't exist, that this file location doesn't exist, or that you can't access this folder, go ahead and generate a new SSH key pair!**
## Generating an SSH key pair
In the command line, type the following by replacing [email protected] with your own email address. Pay attention to spaces and capital letter!
```bash
ssh-keygen -t ed25519 -C "[email protected]"
```
This creates a new SSH key pair, using the provided email as a label.
When you're prompted to "Enter a file in which to save the key," press ENTER. This accepts the default file location.
This is the promt that will appear:
```bash
Generating public/private ed25519 key pair.
Enter file in which to save the key (/Users/username/.ssh/id_ed25519):
```
You will then be asked to provide a passphrase. Protecting your keys with a password is optional but highly recommended. Note: when you type passwords in the command line, nothing is displayed, not even \***.
This is the promt that will appear:
```bash
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
```
When the key generation is complete, you should see the following confirmation:
```bash
Your identification has been saved in /Users/username/.ssh/id_ed25519.
Your public key has been saved in /Users/username/.ssh/id_ed25519.pub.
The key fingerprint is:
SHA256:6nr/zo0g7Bz7WMRwy34maBhQy1UZyX47gT+egRdlIhs [email protected]
The key's randomart image is:
+--[ED25519 256]--+
| .o++ |
| o oF . o |
| . o+ =.+. |
| . + += . |
| . +S++ |
| . ..oB= |
| . ++*=. |
| o.==* o |
| .o.o+** . |
+----[SHA256]-----+
```
## Adding a new SSH key to your GitHub account
We now need to tell GitHub about your public key. Display the contents of your new public key file with `cat`.
**Be careful**: do not copy the content of your *private* key, but your *public* key. Your public key ends with `.pub`.
Please type the command below exactly as it is, in its entirety:
```bash
cat ~/.ssh/id_ed25519.pub
```
The output should look something like this:
```bash
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFEKiimOpcayfHhlbjmnIBAUX74FY/o20k9yFA16XOLm [email protected]
```
Copy the contents of the output to your clipboard.
Login to github.com and bring up your account settings by clicking on your profile photo (top right) and selecting **Settings**. Click on **SSH and GPG keys** (left sidebar), and then click on the green button 'New SSH key' or '**Add SSH key**'.
In the "Title" field, add a descriptive label for the new key, e.g. something that would identify the device you just connected. For example, if you're using a personal laptop, you might call this key "Personal MacBook Air". Finally, paste the contents of your clipboard into the Key text box and hit the green 'Add key' button to save. Enter your GitHub password if prompted.
## Adding your key to the ssh-agent
To manage your keys, it is best to use a piece of software called `ssh-agent`.
Depending on your system, the following might not be necessary. On
most GNU/Linux distributions, your key will be automatically added to
the `ssh-agent` after the first time you enter it. If you keep getting
asked for your key each time you want to clone or push to a GitHub
repository, you can follow the following instructions.
In the command line, start the ssh-agent with this command:
```bash
eval "$(ssh-agent -s)"
```
which should display an output similar to something like this:
```bash
Agent pid 59566
```
Then, add your key to the ssh-agent by typing the entirety of this command:
```bash
ssh-add ~/.ssh/id_ed25519
```
That's it !
Going forward, you can use the SSH clone URL when copying a repo to your local machine (we will cover this in the second tutorial). You are completely done with the setting up part, which you will need to repeat only if you change computer.
Let the fun begin!
***