From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Subject: RE: RFC: update hook for GPG signed submission on secured branches
Date: Fri, 16 Jan 2015 14:47:25 -0500 [thread overview]
Message-ID: <BD3DE7B299FE458287DC8C829CEADEC2@black> (raw)
In-Reply-To: <xmqqsifa1px6.fsf@gitster.dls.corp.google.com>
> -----Original Message-----
> From: Junio C Hamano
> Sent: Friday, January 16, 2015 14:33
>
> "Jason Pyeron" <jpyeron@pdinc.us> writes:
>
> > What would you change? Any bugs that you see?
>
> > sigkey=$(\
> > git cat-file $newrev -p |\
>
> "-p" being a command line option should come before revision, but
> more importantly, because you accept pushes only to refs/heads/, you
> would want to explicitly require commit objects, no? i.e.
>
> git cat-file commit "$newrev" |
True.
>
> I am not sure if you need these unsightly backslashes. When you
> stop talking to it after saying "$(", or "$( git cat-file ... |",
> the shell _knows_ that you haven't stopped what you want to tell
> it.
>
> > sed -e '/^ /{H;$!d;}; x;/^gpgsig /!d; s/^gpgsig//;' |\
> > cut -c 2- |\
>
> It always makes me feel nervous to see people pipe sed output to
> another filter that is a mere s/.//;
It was a very quick Lego block build.
>
> Is this complex pipeline the same as this (I didn't understand the
> trailing I at the end)?
Case insensitive, could have used [0-9a-fA-F].
>
> git cat-file commit "$newrev" |
> sed -ne '/^gpgsig /,/^ -----END/{
> s/^gpgsig //
> s/^ //p
> }' |
Will all future signature values end with a "^ -----END"? I was only going on the assumption that continuation lines start with a single space.
> gpg --list-packets --textmode |
> sed -ne '/^:signature packet:/s/.*keyid \([0-9A-F]*\).*/\1/p'
>
> > gpg --list-packets --textmode |\
> > sed '/keyid/!d; s/.*keyid \([0-9A-F]\{16\}\).*/\1/I' \
> > )
>
> > if [ -z "$sigkey" ]; then
> > echo no GPG signature on commit $newrev
> > exit 1
> > fi
>
> I am not sure if the design of this, to require signature only on
> the tip commit, is sound. That is not a -bug- in the script,
> though.
It is to handle the "all my devs worked on this, they do ________ GPG", so as long as the tip os signed, it is an implicit I am responsible for what is submitted.
>
> > if [[ $refname != refs/heads/* ]]; then
> > echo only heads may be pushed, illegal ref: $refname
> > exit 1;
> > fi
> >
> > head="${refname:11}"
>
> It is hard to tell where the magic number 11 comes from. Perhaps
>
> head="${refname#refs/heads/}"
>
> reads easier?
Much.
Thanks!
-Jason
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
next prev parent reply other threads:[~2015-01-16 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 19:03 RFC: update hook for GPG signed submission on secured branches Jason Pyeron
2015-01-16 19:33 ` Junio C Hamano
2015-01-16 19:41 ` Junio C Hamano
2015-01-16 19:47 ` Jason Pyeron [this message]
2015-01-16 19:59 ` John Keeping
2015-01-16 22:49 ` 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=BD3DE7B299FE458287DC8C829CEADEC2@black \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).