getsops / getsops/sops

keyserver should warn if no gpgkey available

Open
#340 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
23.1k
Forks
1.1k
Avg merge
1d 11h
Merged PRs (30d)
9

Description

If the user has gpg-agent (true with modern gpg) running, but the needed gpg key has not been loaded into the agent, any sops decryption will fail.

The sops error messages just indicate gpg failure, but not a failure to receive a key. The keyserver output reports as "decryption failed", rather than a "key not available" error. E.g.:

[PGP]    INFO[0206] Decryption failed                             fingerprint=xxx

I believe a "key not available" message would be more helpful in pointing the user to the likelihood they haven't added their gpg key locally.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the keyserver's handling of the reported "decryption failed" output and reproduce the case where gpg-agent lacks the needed key. Done means the output distinguishes an unavailable key from a general decryption failure and points the user toward loading the key locally.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.