keybase / keybase/keybase-issues
Can't revoke and push new key.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I recently got a new machine, and lost my keys by accident. I generated a new key locally:
```
$ gpg --gen-key
```
Which works fine:
```
$ tree ~/.gnupg ~
.gnupg
├── gpg.conf
├── pubring.gpg
├── pubring.gpg~
├── random_seed
├── secring.gpg
└── trustdb.gpg
$ gpg -K
/home/marco/.gnupg/secring.gpg
------------------------------
sec 2048R/406F0AF9 2015-11-01
uid Marco Vermeulen
ssb 2048R/A3FF438D 2015-11-01
```
I'm logged in with the keybase cli, and then revoke:
```
$ keybase revoke
Your keybase login passphrase: ***************
- run scrypt [==================================] 100%
error: the user marcovermeulen doesn't have a local key
```
Which of course is not true as I just generated one.
When I then try the alternative of pushing my local key, it complains:
```
$ keybase push --update
info: Updating both remote keys with local version
error: `gpg` exited with code 2
warn: gpg: error reading key: secret key not available
```
I'm running on Ubuntu 15.04 with gpg 1.4.18 using ZSH 5.0.7. Keybase client installed on Node 4.2.1
Any ideas?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported sequence with `gpg --gen-key`, `keybase revoke`, and `keybase push --update` in the stated Ubuntu, GPG, ZSH, and Node environment. Trace how the CLI checks for a local key and invokes GPG; done means the newly generated key can be revoked or pushed without the reported local-key and secret-key errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, ubuntu, zsh
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100