keybase / keybase/keybase-issues

Misleading instructions for uploading public key

Open
#1,936 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

When I go to upload my **public** key, the page suggests the following commands to display my public key:

```
# tip: first list your keys in GPG
gpg -K --keyid-format long --with-colons --with-fingerprint
# then export the one you want (look next to `fpr`)
gpg --export -a A4AA3A5BDBD40EA549CABAF9FBC07D6A97016CB3
```

The first command uses the long form arguments for everything except the `-K`, which checking the man page tells me it is for listing the **secret** key, not the **public** key. As far as I can tell, there is only one fingerprint for the public/secret pair, so there is no need to use `-K` or `--list-secret-keys` and the instructions could be changed to the following:

```
# tip: first list your keys in GPG
gpg --list-keys --keyid-format long --with-colons --with-fingerprint
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the public-key upload page and locate the GPG instructions shown when uploading a public key. Compare the key-listing command with the issue's proposed public-key form, then verify that the displayed instructions consistently list and export the intended public key.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.