keybase / keybase/keybase-issues
Integration/support of HKP/GPG WoT
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
With GPG we already have central registries, the GPG key servers, where people push keys to using the HKP protocol. It has the added advantage that most servers are also set up to sync with each other.
My main concern is that Keybase is causing a split-brain situation if I use the same key on public key servers and Keybase. My key, uploaded to Keybase gets tracked by someone else on Keybase but since there doesn't seem to be an HKP sync that information is never updated for the rest of the world. Similarly if someone signs my GPG key the 'traditional' way key base isn't aware of this until I re-upload my public key (I'm not sure if this would even work).
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names HKP, GPG key servers, Keybase, and WoT but identifies no files, tests, or entry point. Start by determining the intended synchronization behavior and scope; the issue does not define a concrete completion condition.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100