Bad key found: no private key material or GPGKey
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
[write something useful and descriptive here]
Unable to login to app. I am, however, using my own generated GPG key that has the master signing key separated off-system. I have a separate signing subkey used for everything aside from trust signing, does that makes a difference?
There was an error provisioning
Unknown error: Bad key found: no private key material or GPGKey
my log id: 2b9db13d0e23bea0ffcf0b1c
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 login provisioning flow that reports “Bad key found: no private key material or GPGKey,” using the supplied log ID and the generated GPG key with its signing subkey. Determine whether this key layout is supported and document or fix the provisioning behavior so login succeeds or reports the required key material clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100