Git SSH Keys ​
Git SSH Keys holds the key pairs your account uses to reach private Git repositories. A public repository needs no key; a private one on GitHub, GitLab, or your own server does.
Overview ​
URL: /client/git-ssh-keys
The page sits under Software, next to Git Version Control.
Adding a key ​
Create Git SSH Key asks for a name and a key pair.
| Field | What it is |
|---|---|
| Name | A label, so you can tell one key from another later. |
| Private Key | The half that stays here. |
| Public Key | The half you give to the Git host. |
Generate creates a fresh pair for you and fills both fields. Use it unless you have a reason to reuse an existing key: a key generated here is used by this account only, so revoking it later affects nothing else you own.
After creating the key, copy the public half into your Git host, as a deploy key on the repository or as an account key. Never paste the private half anywhere outside this page.
Name keys after what they are for, such as the repository or the host. A list of keys called key1 and key2 is impossible to clean up safely a year later.
Removing a key ​
Removing a key stops this account reaching anything that trusted it. Remove the matching entry at the Git host as well, otherwise a key you have retired here is still listed as trusted there.
Related pages ​
- Git Version Control - the repositories these keys reach.
- SSH Terminal - shell access, which uses its own access settings.
- Applications - what you might deploy from a repository.