From 9868a2e1509308f8c3bfe0ed725d0ed6b93f73fb Mon Sep 17 00:00:00 2001 From: David Anselmi Date: Sun, 28 Jun 2026 00:11:20 +0200 Subject: [PATCH] Clarify ssh-keygen use. (#807) 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 --- content/security/ssh-key.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/security/ssh-key.md b/content/security/ssh-key.md index ee68715..42ee878 100644 --- a/content/security/ssh-key.md +++ b/content/security/ssh-key.md @@ -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.