revoked key suggested during 'keybase pgp select'
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
a la:
$ keybase pgp select
# Algo Key Id Created UserId
= ==== ====== ======= ======
1 4096R 1535F82E8083A84A Chris Weyl <cweyl@alumni.drew.edu>, Chris Weyl <rsrchboy@cpan.org>, Chris Weyl <chris.weyl@gmail.com>, Chris Weyl <chris@chrisweyl.com>, Chris Weyl <chris@whitepointstarllc.com>, Chris Weyl <chris.weyl@wps.io>, Chris Weyl <chris.weyl@wps.io>, Chris Weyl <cweyl@alumni.drew.edu>
2 4096R 868E947777178EBD Chris Weyl <chris.weyl@dreamhost.com>
Choose a key:
In this case, key 2 has been revoked (tho the secret key is still present).
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 at the implementation or entry point for the keybase pgp select command and reproduce the issue with a revoked key whose secret key remains present. Determine the intended selection behavior from the command output; done should be confirmed when revoked keys are no longer suggested, with coverage for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100