keybase / keybase/keybase-issues

keybase pgp push-private ERROR

Open
#4,249 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

1. Installed keybase on Macbook Pro (M1)
2. Generated new pgp key
3. Need use this pgp key on other Macbook
4. `keybase pgp push-private `
5. After that I have error:

> `keybase pgp push-private ***********************************
PLEASE READ THIS CAREFULLY -- PRIVATE KEYS ARE AT STAKE!
This command will export PGP private keys from GnuPG and write them
to KBFS, in your private directory under .keys/pgp. After the operation
completes, they will be available on all of your Keybase devices, on which
you can run keybase pgp pull-private to sync them to your GnuPG keychain.
The goal is to securely move your PGP private key across your devices. Note
all uploads are encrypted for all of your devices using device keys and therefore
are not susceptible to brute-force passphrase guessing attacks. An attacker
would need access to one of your unlocked Keybase devices to access your PGP
private key.
Really push your PGP private key to KBFS? (type 'YES' to confirm): YES
▶ ERROR GPG error: exit status 2

my log id: 83fd14692b5641b877c03c1c

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `keybase pgp push-private ` on the reported MacBook Pro M1 setup after generating a PGP key. Use log ID 83fd14692b5641b877c03c1c to inspect the GPG failure; done means the private key is pushed successfully and can be retrieved with `keybase pgp pull-private` on another device.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
cryptography, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.