PGP key issue
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hi! Logged in to the website after a long time and trying to encrypt a message for the same account (cointree). A error shows "Error: Cannot find a public key for 'cointree'."
So, we tried "add a PGP key" on the website. After letting the website generate keys, the dialog closes without any messages or changes to the account.
Then, tried logging in using cmd. After naming the device, we receive "ERROR signing_kid 01015b58c... not found"
It seems the account has lost the keys (or maybe expired) and unable to generate new ones? Or, are we missing something here?
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
The report concerns the website’s “add a PGP key” flow and command-line login, with errors about a missing public key and signing_kid. Start by reproducing both paths for the affected account; done means determining why key generation or key lookup fails and verifying the behavior after the account’s keys are restored or regenerated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100