Can't select GPG key
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Running keybase pgp select gives me an error. It first lists my keys, when I select one, it fails with
2020-01-29T10:29:24.268298-07:00 ▶ [ERRO keybase main.go:87] 118 key generation error: no valid primary key self-signature or key(s) have expired (Signature failure in packet 1: rejecting insecure hash SHA1 (XYXYXYXYXY)) (error 905)
My key never expires, ie.:
/home/xxx/.gnupg/pubring.kbx
------------------------------
pub rsa2048 2013-11-10 [SC]
XYXYXYX
uid [ultimate] XXX YYY <zzz@zzz>
uid [ultimate] XXX YYY <vvv@vvv>
sub rsa2048 2013-11-10 [E]
➜ ~ gpg --edit-key ????
gpg (GnuPG) 2.2.19; Copyright (C) 2019 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Secret key is available.
sec rsa2048/XYXYXYXY
created: 2013-11-10 expires: never usage: SC
trust: ultimate validity: ultimate
ssb rsa2048/XYXYXYXYXYXY
created: 2013-11-10 expires: never usage: E
[ultimate] (1). XXX YYY <zzz@zzz>
[ revoked] (2) fff <fff@fff>
[ultimate] (3) XXX YYY <vvv@vvv>
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
Start with the keybase pgp select command and the reported GPG error about rejecting SHA1 signatures. Trace how the selected key is validated and compare that behavior with the key details shown by gpg --edit-key. Done means selecting this non-expiring key no longer fails, with the relevant behavior covered by a test if the existing command tests identify a suitable location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100