Skip to content

Commit 1a728ec

Browse files
Update github-ssh-access.md
1 parent 31256b5 commit 1a728ec

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

recipes/shell/ssh/github-ssh-access.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,16 @@ How to set up SSH on your machine from scratch and configure SSH access on your
88

99
## Why
1010

11-
If you set up GitHub SSH access, then you can clone, push or pull using an SSH repo URL. Note the URL does not start with `https`, unlike the usual **HTTP(* accesd method, which is less secure.
11+
If you set up GitHub SSH access, then you can clone, push or pull using an SSH-style URL. Note the URL does not start with `https`, unlike the usual **HTTP** access method, which is less secure as it needs a password or token.
12+
Using SSH means you allow an SSH key-pair for a specific device, unlike a password or token which can be reused anywhere.
1213

1314
e.g.
1415

1516
```sh
1617
$ git clone git@github.com:MichaelCurrin/code-cookbook.git
1718
```
1819

19-
This avoids having to enter your **password** each time your push, or if you pull a private repo. And this is especially useful if **2FA** is setup.
20+
This avoids having to enter your **password** each time your push, or if you pull a private repo. And this is especially useful if **2FA** is setup as you would have to add your code from Google Authenticator or similar on every push.
2021

2122
You can also use the SSH URL for any **public** repos by other people if you want to clone them (you won't be able to push unless you are a collaborator though).
2223

0 commit comments

Comments
 (0)