From: Junio C Hamano <gitster@pobox•com>
To: Michael J Gruber <git@drmicha•warpmail.net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 0/5] Documentation/technical: describe signature formats
Date: Fri, 17 Jun 2016 10:38:01 -0700 [thread overview]
Message-ID: <xmqqeg7v1zt2.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <cover.1466148698.git.git@drmicha.warpmail.net> (Michael J. Gruber's message of "Fri, 17 Jun 2016 09:46:07 +0200")
Michael J Gruber <git@drmicha•warpmail.net> writes:
> - We don't support verifying push certificates, although they fit in with
> git verify-tag. Patch has been submitted, and this series documents the
> result already (git verify-tag --blob).
>
> - We don' support verifying signed merge tags other than by using log/show,
> which is not quite fit for scripting.
Both true and are good things to tackle, I would think.
It would be ideal if we can unify the latter with verification of
signed commits.
> - We have signature parsing code all over the place, including places that
> should probably abstract more, such as tag.c and log-tree.c.
Looking forward to see the result of that new abstraction.
> - We may want to give more support for deciding about the trustworthiness
> of signatures, the same way we export information to receive hooks
> in the presence of push certificates. (Give information, don't decide.)
Again, true.
Thanks for starting this.
> Michael J Gruber (5):
> Documentation/technical: describe signature formats
> Documentation/technical: signed tag format
> Documentation/technical: signed commit format
> Documentation/technical: signed merge tag format
> Documentation/technical: push certificate format
>
> Documentation/Makefile | 1 +
> Documentation/technical/signature-format.txt | 242 +++++++++++++++++++++++++++
> 2 files changed, 243 insertions(+)
> create mode 100644 Documentation/technical/signature-format.txt
prev parent reply other threads:[~2016-06-17 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 7:46 [PATCH 0/5] Documentation/technical: describe signature formats Michael J Gruber
2016-06-17 7:46 ` [PATCH 1/5] " Michael J Gruber
2016-06-17 7:46 ` [PATCH 2/5] Documentation/technical: signed tag format Michael J Gruber
2016-06-17 7:46 ` [PATCH 3/5] Documentation/technical: signed commit format Michael J Gruber
2016-06-17 7:46 ` [PATCH 4/5] Documentation/technical: signed merge tag format Michael J Gruber
2016-06-17 7:46 ` [PATCH 5/5] Documentation/technical: push certificate format Michael J Gruber
2016-06-17 8:54 ` [PATCHv2] " Michael J Gruber
2016-06-17 19:14 ` Junio C Hamano
2016-06-17 17:38 ` Junio C Hamano [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=xmqqeg7v1zt2.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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