keybase track <name> result different from gpg --import <key file>
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I have a case where the key added to my gpg keychain is slightly different depending on whether I use:
keybase track
or download the .asc file from the website and import it directly using:
gpg --import
If I check the list of User IDs using GPG, when I imported the key using keybase I get a smaller list of addresses than when I imported the key using gpg (3 from the keybase track, 6 from the gpg import).
This may be expected behaviour; it just seems kind of odd.
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
Reproduce the reported difference between keybase track <name> and importing the downloaded .asc file with gpg --import <file>. Compare the resulting GPG user ID lists, then determine whether the three-versus-six address discrepancy is expected or indicates a bug in the Keybase client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100