keybase / keybase/keybase-issues
add a pgp key with web UI inadequate instructions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
When trying to upload an existing key the instructions are:
# 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')
Never mind, that "fpr" is actually surrounded by accent graves instead of single quotes.
But which fingerprint is one supposed to use?
$ gpg -K --keyid-format long --with-colons --with-fingerprint | grep fpr:
fpr:::::::::0EBFBCCA3E540AD481817E16B09B16FAED079011:
fpr:::::::::B01B7C04DDF8799A9DFEA518CC28563136617E99:
fpr:::::::::B892A45A8332FFE0EF849213F9E0F61E7079FB55:
fpr:::::::::F3824D9466AA166BF014F6E65C5AB09657CF17A9:
fpr:::::::::9EADFA9F4D95AEE145A764B752DAC5FE559A59C0:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the web UI instructions for uploading an existing key and the shown gpg -K --keyid-format long --with-colons --with-fingerprint command. Clarify the quoted fpr reference and identify which fingerprint the user should use; done means the instructions resolve the ambiguity.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100