keybase / keybase/keybase-issues

keybase gen fails under GPG v1.4.x with `trust-model always` in config

Open
#309 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

The reason is that with this flag, we don't have any scrapable output from gpg about what the fingerprint of the most recent key is. See #307 for other examples of this failure that we've been able to solve.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing this failure with the examples in issue #307 and reproducing `keybase gen` with GPG v1.4.x and `trust-model always` in the configuration. The work is done when key generation reliably determines the most recent key's fingerprint and succeeds in this configuration.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.