dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-08-15 14:53:29 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Clarify ssh-keygen use. (#807)

Browse source 
Closes #411. I don't think a larger change is warranted here. The directions provided by settings/keys could be better but that's a separate issue (probably for Forgejo). Thanks!

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/807
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
This commit is contained in:
David Anselmi 2026-06-28 00:11:20 +02:00 committed by Gusted
parent 9ef2d7113b
commit 9868a2e150
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

@ -155,7 +155,7 @@ added key is yours.
1. Go to the [SSH/GPG Keys tab](https://codeberg.org/user/settings/keys) in your Codeberg settings.
2. Click on the **Verify** button next to the SSH key you would like to verify.
3. Codeberg will show a token. Under its text box copy the command, and replace `/path_to_your_private_key` with the
correct path of your private key.
correct path of your private (or public) key. (Either key works, ssh-keygen will do the right thing.)
4. Copy the output, beginning with `-----BEGIN SSH SIGNATURE-----` and ending with `-----END SSH SIGNATURE-----`.
5. Paste it into the large textbox and click the **Verify** button.