keybase / keybase/keybase-issues
Can't track one user
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I’m "timbray" and at https://keybase.io/timbray it says I’m tracking "paulehoffman" and "ericajoy". If I say
keybase encrypt ericajoy -m 'alpha beta gamma'
it goes ahead, lists the proofs, says I’ve OK’ed then, and creates the mesage
If I say
keybase encrypt paulehoffman -m 'alpha beta gamma'
info: ...checking identity proofs
✔ public key fingerprint: F4EE 5B0D 940F 7190 7A59 83D1 B199 C2A1 E10F 457B
✔ "paulehoffman" on twitter: https://twitter.com/paulehoffman/status/446040345193639936
✔ "paulehoffman" on github: https://gist.github.com/9630485
Is this the paulehoffman you wanted? [y/N]
So for some reason, the "track" operation isn't working in this case.
Hint: Paul used his own GPG key, he told me.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the two reported `keybase encrypt` commands and compare their tracking and identity-proof behavior, using the Keybase profile and GPG-key detail in the report as context. Trace the `track` operation and encryption command path; done means a tracked user no longer prompts for confirmation when the tracked identity is valid, with regression coverage for this case.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100