keybase / keybase/keybase-issues

Tracking question: New/Old Public Key Fingerprint

Open
#2,032 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

Hi folks.

I have several users that I've been tracking for a few months that suddenly no longer have PGP fingerprints associated with them. If I do `keybase list-tracking -v`, there are no fingerprints listed (though other proofs are). If I `keybase id` one of these users, the fingerprint has a "" in front of it, instead of a "" (and again, these users do have other proofs that are listed as tracked).

I tracked several users recently that do list the fingerprints, in addition to their other proofs.

I'm fairly certain that the actual fingerprint hasn't changed, because if I look at, for instance, a github proof (which is listed as tracked), it will list the correct fingerprint.

I recently uninstalled the npm version and installed the CLI with homebrew. I guess it's possible that these were never tracked, but I'm not sure I understand why that would be the case. It's also possible/likely I don't understand tracking.

Thoughts?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the discrepancy with `keybase list-tracking -v` and `keybase id` for an affected user, comparing the PGP fingerprint with the tracked GitHub proof. Done means determining why the fingerprint is shown as `` rather than `` and documenting the tracking state or behavior that explains it.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.