git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Bad experience with gpg signing failures

From
SPStan Pitucha <stan.pitucha@envato.com>
Date
Apr 24, 2020, 00:23 UTC
Message-ID
<CAJ2_uEOk8xoLvK8B8PYc0_=kA8W_LqKwGyhKghemQDdRzA2nFA@mail.gmail.com>

Hi all, There are two issues I keep running into with gpg signing usability:

1. When gpg fails to sign the commit, the error message is not
forwarded. That means you always get "gpg failed to sign the data"
when the actual gpg error is for example "gpg: skipped ...: Unusable
secret key". This makes the errors hard to deal with, because you
don't know which command actually failed without GIT_TRACE. That's
especially bad in case of transient errors.
2. When gpg fails to sign the commit, it's not reported where it's
available. I found that it's possible to recover it from
COMMIT_EDITMSG from man pages, but it would be great if "gpg failed to
sign the data" message was followed with "your message draft was saved
to .git/COMMIT_EDITMSG" to make it more discoverable / not require
reading full manual to find out about it.
-- 
Stan Pitucha


Site Reliability Engineer at Envato

http://envato.com


The email and any attachments are confidential and may contain
information that is exempt from disclosure by law and subject to
copyright. If you have received this message in error please let me
know and delete it.
Message 1 of 1 in “Bad experience with gpg signing failures”
  1. Stan PituchaApr 24, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.