keybase pgp drop doesn't warn to generate revocation certificate
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
$ keybase version
Client: 1.0.16-20160713110422+a1c00b3
Service: 1.0.16-20160713110422+a1c00b3
$ keybase pgp drop "0101cbea3f0835743a39b13908ea7e7bfac05e32e685417637d099d714fc441eca530a"
- INFO Revoking KIDs:
- INFO 0101cbea3f0835743a39b13908ea7e7bfac05e32e685417637d099d714fc441eca530a
$ keybase pgp help drop
NAME:
keybase pgp drop - Drop Keybase's use of a PGP key
USAGE:
keybase pgp drop <key-id>
DESCRIPTION:
"keybase pgp drop" signs a statement saying the given PGP
key should no longer be associated with this account. It will **not** sign a PGP-style
revocation cert for this key; you'll have to do that on your own.
Where is the revoking certificate the cli tool is telling me? Or is the pgp drop command output misleading?
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 with the keybase pgp drop command and compare its reported “Revoking KIDs” output with the keybase pgp help drop description. Determine whether the command creates a PGP revocation certificate or only revokes the Keybase association; done means the output and help text accurately describe that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cryptography
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100