dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-06-16 05:13:54 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Use full path when specifying ssh key file (#669)

Browse source 
Using a `~` apparently does not work with `ssh-keygen`:
```
$ ssh-keygen -t ed25519 -a 100
Generating public/private ed25519 key pair.
Enter file in which to save the key (/home/knud/.ssh/id_ed25519): ~/.ssh/id_ed25519_codeberg
Enter passphrase for "~/.ssh/id_ed25519_codeberg" (empty for no passphrase):
Enter same passphrase again:
Saving key "~/.ssh/id_ed25519_codeberg" failed: No such file or directory
```

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/669
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: hugobuddel <hugo@buddelmeijer.nl>
Co-committed-by: hugobuddel <hugo@buddelmeijer.nl>
This commit is contained in:
hugobuddel 2025-09-06 14:00:07 +02:00 committed by Bastian Greshake Tzovaras
parent 224d96e4a7
commit cff67c76cb
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/security/ssh-key.md
View file

@ -43,7 +43,7 @@ your laptop and your office PC you should generate separate keys for each machin
ssh-keygen -t ed25519 -a 100
```
3. This time, enter a new filepath when prompted (e.g., `~/.ssh/id_ed25519_codeberg`) to avoid overwriting the
3. This time, enter a new filepath when prompted (e.g., `/home/knut/.ssh/id_ed25519_codeberg`) to avoid overwriting the
existing key.
4. You will be asked for a passphrase; enter one if you'd like, or leave the prompt empty.