`keybase pgp list` does not indicate revocation status
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Sample output:
$ keybase pgp list
Keybase Key ID: 010135221647a4fc94701ae8b445d7e522d949577e2368a089394a7fe3b2d37019f30a
PGP Fingerprint: 28A8 F8D3 3491 1B02 55D8 F334 81FD DC30 10CF D9F6
PGP Identities:
[…]
Keybase Key ID: 0101acb619188f6c1d06bf639e2236bf62fd0f4ffca0b0cc4926aaf23b9ead304bc90a
PGP Fingerprint: 3874 2D65 D1CD 2A38 44E0 BA6F 7800 AAE1 DFC5 FDBF
PGP Identities:
[…]
The first of these has been revoked. In my opinion, the output should note this fact, preferably including the revocation reason and possibly also the associated comment, if any.
Keybase version: 1.0.18-20170306170025+9d4a393.
See also #4574, keybase/keybase-issues#2893.
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 tracing the keybase pgp list command and how it formats each PGP key. Check how the command can identify the revoked key in the sample output, then run the relevant PGP-listing tests or command to verify that revocation status is shown with its reason and any associated comment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100