All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Not Sure <kuerzn@googlemail.com>
Cc: <git@vger.kernel.org>
Subject: Re: GnuPG commit signature verification ignores GPG's status-fd and status-file options
Date: Tue, 9 Apr 2013 17:22:54 +0200	[thread overview]
Message-ID: <87vc7vlodt.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <5164027C.4020007@googlemail.com> (Not Sure's message of "Tue, 09 Apr 2013 13:58:52 +0200")

Not Sure <kuerzn@googlemail.com> writes:

> Starting with the newest git version 1.8.2.1, the signature checking
[...]
> 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

      reply	other threads:[~2013-04-09 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 11:58 GnuPG commit signature verification ignores GPG's status-fd and status-file options Not Sure
2013-04-09 15:22 ` Thomas Rast [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vc7vlodt.fsf@linux-k42r.v.cablecom.net \
    --to=trast@inf.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=kuerzn@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.