keybase / keybase/keybase-issues
Show a fingerprint instead of Key IDs
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Key IDs are far less collision proof than the actual SHA-1 fingerpints themselves. It has been demonstrated multiple times that it isn't a hard problem to produce keys which have the same key ID as another key.
In my oppinion, the whole idea of key IDs is flawed and should have never been introduced. Now that we know that, could we please discourage their use by banning them from our user interfaces for all eternity?
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
The issue names no files, tests, or entry points. First inventory the user interfaces that display Key IDs and clarify whether all should show SHA-1 fingerprints instead; done means the agreed interfaces no longer expose Key IDs and the replacement behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, frontend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100