keybase / keybase/keybase-issues

Default key template should be changed. Current template breaks LDAP and/or HKP use. @keybase.io email doesn't go anywhere and gives no identity context

Open
#524 5 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

When `keybase` or web client create a new key, the format of that key is something like:

```
pub 4096R/B73E8516 2014-03-28
uid keybase.io/zqueal
```

This key has no real name and an email address that goes nowhere (at the moment). If uploaded to a public keyserver (http://pgp.mit.edu, http://keyserver.ubuntu.com, etc) it is completely useless for users who have an email client that queries keyservers (as in https://github.com/keybase/keybase-issues/issues/327)

Instead, the name and email address used during account creation should be used in a template like:

```
pub 4096R/8133F0FD 2014-04-05 [expires: 2015-04-05]
uid Brian Pugh (https://keybase.io/bpugh)
```

This provides the ability to tie key identity to keybase identity (as in https://github.com/keybase/keybase-issues/issues/521) as well as better integration into the existing keyserver ecosystem (as in https://github.com/keybase/keybase-issues/issues/327)

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or code entry points are mentioned. Start by locating the key-generation path used by the keybase client or web client, then trace how account name and email values are selected; done means newly created keys use an identity-bearing name and reachable email while preserving keyserver compatibility.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.