From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Karel Kočí" <karel.koci@nic.cz>,
"Santiago Torres" <santiago@nyu.edu>,
"Vojtech Myslivec" <vojtech.myslivec@nic.cz>,
git@vger.kernel.org
Subject: Re: [PATCH 1/1] verify-tag/verify-commit should exit unsuccessfully when signature is not trusted
Date: Thu, 9 Aug 2018 15:50:26 -0400 [thread overview]
Message-ID: <20180809195026.GD32376@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqy3dfbcys.fsf@gitster-ct.c.googlers.com>
On Thu, Aug 09, 2018 at 11:40:27AM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > I guess leaving it serves as a sort of cross-check if gpg would return a
> > zero exit code but indicate in the status result that the signature was
> > not good. Sort of a belt-and-suspenders, I guess (which might not be
> > that implausible if we think about somebody wrapping gpg with a sloppy
> > bit of shell code that loses the exit code -- it's their fault, but it
> > might be nice for us to err on the conservative side).
>
> OK, this time a real log message.
>
> -- >8 --
> Subject: [PATCH] gpg-interface: propagate exit status from gpg back to the callers
> [...]
Thanks, the explanation and the patch look good to me.
I'm on the fence over whether a follow-up patch to take away the "U" is
worth it. In practice the code should never trigger either way, since
gpg would already have exited non-zero in such a case.
-Peff
next prev parent reply other threads:[~2018-08-09 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 20:05 [PATCH 1/1] verify-tag/verify-commit should exit unsuccessfully when signature is not trusted Vojtech Myslivec
2018-08-01 0:19 ` brian m. carlson
2018-08-01 0:25 ` Santiago Torres
2018-08-03 13:36 ` Karel Kočí
2018-08-03 15:43 ` Santiago Torres
2018-08-03 16:06 ` Jeff King
2018-08-04 8:43 ` Karel Kočí
2018-08-08 23:04 ` Jeff King
2018-08-08 23:12 ` brian m. carlson
2018-08-09 0:59 ` Junio C Hamano
2018-08-09 1:43 ` brian m. carlson
2018-08-09 14:30 ` Jeff King
2018-08-09 15:30 ` Junio C Hamano
2018-08-09 17:12 ` Jeff King
2018-08-09 18:40 ` Junio C Hamano
2018-08-09 19:50 ` Jeff King [this message]
2018-08-10 2:27 ` brian m. carlson
2018-08-13 15:14 ` Vojtech Myslivec
2018-08-03 17:32 ` Junio C Hamano
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=20180809195026.GD32376@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karel.koci@nic.cz \
--cc=sandals@crustytoothpaste.net \
--cc=santiago@nyu.edu \
--cc=vojtech.myslivec@nic.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).