keybase / keybase/keybase-issues
"keybase pull" should update GPG keyring for tracked users
Open
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
When I track users, my intuition is that `keybase pull` should bring their pubkeys into my GPG keychain. Am I misunderstanding something important?
```
Brians-MBP-2:web3 topping$ keybase version
keybase (keybase.io CLI) v0.7.3
- node.js v0.10.35
- gpg (GnuPG/MacGPG2) 2.0.26
- libgcrypt 1.6.2
Identifies as: 'keybase.io node.js client v0.7.3 darwin'
```
Contributor guide
No contributing guide indexed for this repository
Research direction
The report identifies `keybase pull` as the entry point and GPG/MacGPG2 as the environment. Verify the intended behavior for tracked users and confirm that their public keys are present in the GPG keychain after the command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100