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

Re: GnuPG commit signature verification ignores GPG's status-fd and status-file options

From
Thomas Rast <trast@inf.ethz.ch>
Date
Apr 9, 2013, 15:22 UTC
Message-ID
<87vc7vlodt.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<5164027C.4020007@googlemail.com>
Not Sure <kuerzn@googlemail.com> writes:
> Starting with the newest git version 1.8.2.1, the signature checking
[...]
Show 7 quoted lines
> Missing from output is the machine parsable GPG information:
>
> [GNUPG:] SIG_ID sorvifhoerui/asidunb 2013-04-09 23947273
> [GNUPG:] GOODSIG 433811111111111324 User <usermail>
> [GNUPG:] VALIDSIG ddddddddddddddddddfsjidjfv 2013-04-09 aoidfjidh0 0 4 0
> 1 2 00 oshidvoo444444ddddddddd
> [GNUPG:] TRUST_ULTIMATE

I suspect that's because since b60b756 (gpg-interface: check good signature in a reliable way, 2013-02-14), Git parses the above output.

Also, in e290c4b (pretty printing: extend %G? to include 'N' and 'U', 2013-03-31) which is currently in master, this was fixed:

> Note: The git-log format specifiers %GG, %G?, %GK, ... do not provide
> enough information
Is anything else missing?
-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Not Sure
Message 2 of 2 in “GnuPG commit signature verification ignores GPG's status-fd and status-file options”
  1. Not SureApr 9, 2013
  2. Thomas RastApr 9, 2013

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.