It is recommended to use one key per client. This means that if you access your Codeberg repository from your home PC, your laptop and your office PC you should generate separate keys for each machine.
Generating an SSH key pair
Open Terminal on Linux/macOS, or Git Bash on Windows.
Paste the text below:
ssh-keygen -t ed25519 -a 100
This will generate a new SSH key. You can also add a comment to help you identify the client with
-C "comment here".
> Generating public/private ed25519 key pair.
When you're prompted to "Enter a file in which to save the key", press Enter. This accepts the default file location:
> Enter file in which to save the key (/home/knut/.ssh/id_ed25519): [Press enter]
You will be asked for a passphrase; enter one if you'd like, or leave the prompt empty.
Your private key can be protected by a passphrase. This adds a layer of authentication that increases security. Be aware that this will only be helpful for certain attack scenarios and does not offer 100% protection. It is recommended to keep your private key safe and - well - private.
Add the SSH key to Codeberg
Copy the SSH key to your clipboard. You must only copy the public key not the private one. You can identify it by the
.pubsuffix. By default, you can find the public key in
On Linux you can use
xclipon the command line. You may need to install it from your package manager.
$ xclip -selection clipboard < ~/.ssh/id_ed25519.pub
On Windows you can use
$ clip < ~/.ssh/id_ed25519.pub
On macOS you can use
$ pbcopy < ~/.ssh/id_ed25519.pub
These commands will copy the contents of id_ed25519.pub (your SSH public key) to your clipboard.
Alternatively you can locate the hidden .ssh folder, open the file in your favorite text editor, and copy it to your clipboard.
Navigate to your user settings
- Go to the section SSH / GPG Keys and click on Add key.
- Give an appropriate name for the key.
- Paste your key string into Content field.
- Click the Add key button.
You can always access your SSH public keys from
https://codeberg.org/username.keys, substituting in your Codeberg username.
Test the SSH connection
Do this simple test:
$ ssh -T firstname.lastname@example.org
The output should look like this:
Hi there! You've successfully authenticated, but Gitea does not provide shell access. If this is unexpected, please log in with password and setup Gitea under another user.
Note: All Codeberg users share a single Unix user named
git which is used to check out repositories. Depending on the key provided, permission is granted or denied. You can check out all repositories with your key which you have permission for. You can push code to all repositories where you have write access.
Verifying your SSH Key
Anyone can add a random SSH key; but fortunately, Codeberg provides a mechanism to verify that the key belongs to you. Every keypair consists of a public and a private key that are connected to one another. Using this private key, you can sign the provided message. If the signed message is valid, Codeberg can confirm that the added key is yours.
- Go to the SSH/GPG Keys tab in your Codeberg settings.
- Click on the Verify button next to the SSH key you would like to verify.
- Codeberg will show a token. Under its text box copy the command, and replace
/path_to_your_private_keywith the correct path of your private key.
- Copy the output, beginning with
-----BEGIN SSH SIGNATURE-----and ending with
-----END SSH SIGNATURE-----.
- Paste it into the large textbox and click the Verify button.
Avoid re-typing the passphrase
Assuming you've created a secure key with a passphrase, SSH will prompt you for your passphrase for every connection. Common desktop environments like macOS or GNOME will offer you to cache your passphrase via an SSH agent.
If you are working at the command line, you can alternatively do this directly:
$ eval $(ssh-agent) $ ssh-add # enter your passphrase once, then it is cached.
Changing your repository's transport from HTTPS to SSH
Go to the directory where your repository is located:
Look at the existing remotes with
git remote -v
It will look similar to this:
origin https://codeberg.org/knut/foobar.git (fetch) origin https://codeberg.org/knut/foobar.git (push)
You might be using a different name than
originfor your repository. If you do, remember to use that different name in the following steps.
git remote set-urlcommand followed by the remote name and the remote’s URL:
git remote set-url <remote-name> <remote-url>
For example, to change the URL of
email@example.com:knut/foobar.gityou would type:
git remote set-url origin firstname.lastname@example.org:knut/foobar.git
Your HTTPS URL used this format:
https://codeberg.org/<user>/<repo>.gitThe SSH URL uses this format:
ssh://at the beginning like this:
Alternatively, you can find the SSH URL by going to your repository page on Codeberg (for example, going to
https://codeberg.org/knut/foobar), clicking on SSH in the top right corner and copying the URL.
Verify that your change was successful:
git remote -v
The output should look like this:
origin ssh://email@example.com:knut/foobar.git (fetch) origin ssh://firstname.lastname@example.org:knut/foobar.git (push)
This guide is derived from GitHub Docs, used under CC-BY 4.0.