keybase / keybase/keybase-issues

Have KeyBase publish itself as a public KeyServer

Open
#327 150 comments 156 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

It would be an important step in KeyBase adoption IMO, for it to publish itself as a valid keyserver using the standard protocols for such.

As it stands, since keybase doesn't, it means that all the tooling (such as EnigMail for Thunderbird) that has existed for a decade+ ... is unusable against keybase published keys.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue requests that KeyBase publish itself as a public keyserver using standard protocols, so tools such as EnigMail for Thunderbird can use KeyBase-published keys. No files, tests, or entry points are named; first identify the relevant keyserver and protocol integration points. Done means external tooling can consume published KeyBase keys.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.