keybase / keybase/keybase-issues
ERROR key generation error: no valid primary key self-signature or key(s) have expired
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
trying to add my public key into Keybase.
i run `keybase pgp select` from the commandline...
```
You are selecting a PGP key from your local GnuPG keychain, and
will publish a statement signed with this key to make it part of
your Keybase.io identity.
Note that GnuPG will prompt you to perform this signature.
You can also import the secret key to *local*, *encrypted* Keybase
keyring, enabling decryption and signing with the Keybase client.
To do that, use "--import" flag.
Learn more: keybase pgp help select
# Algo Key Id Created UserId
= ==== ====== ======= ======
1 4096R 35A84EDD7D541840 Deviant Ollam
Choose a key: 1
- ERROR key generation error: no valid primary key self-signature or key(s) have expired (Signature failure in packet 1: rejecting insecure hash SHA1 (35a84edd7d541840)) (error 905)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing `keybase pgp select` with the listed key and inspect the signature error, especially the rejected SHA1 hash and expired or invalid primary-key self-signature. No source files or tests are named in the issue; the issue is resolved when the key can be selected and published without the reported error.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100