git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Schleizer <patrick-mailinglists@whonix.org>
Cc: git@vger.kernel.org, Whonix-devel <whonix-devel@whonix.org>
Subject: Re: gpg verify git sub modules useful?
Date: Tue, 28 Feb 2017 09:36:03 -0800	[thread overview]
Message-ID: <xmqqmvd6kykc.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <a9da4416-6437-a491-f461-c5e61d805b2d@riseup.net> (Patrick Schleizer's message of "Tue, 28 Feb 2017 15:50:00 +0000")

Patrick Schleizer <patrick-mailinglists@whonix.org> writes:

> When using git submodules, is there value in iterating about the git
> submodules running "git verfiy-commit HEAD" or would that be already
> covered by the git submodule verification?

That depends on what you are referring to with the "git submodule
verification" and more importantly what threat you are guarding
against.  "git -C <submodule-dir> verify-commit HEAD" may make sure
that the contents of that commit object is GPG signed by whoever you
trust--is that what you want to make sure?  Or do you want all
commits in the submodule history to be similarly signed because the
tree of the superproject can switch to some other commit there?

  reply	other threads:[~2017-02-28 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 15:50 gpg verify git sub modules useful? Patrick Schleizer
2017-02-28 17:36 ` Junio C Hamano [this message]
2017-03-01 18:28   ` Patrick Schleizer
2017-03-01 19:08     ` Stefan Beller

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqmvd6kykc.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=patrick-mailinglists@whonix.org \
    --cc=whonix-devel@whonix.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).