All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>,
	"Joseph Parmelee" <jparmele@wildbear.com>,
	"Carlos Martín Nieto" <cmn@elego.de>,
	"Olsen, Alan R" <alan.r.olsen@intel.com>,
	"Michael Witten" <mfwitten@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Lack of detached signatures
Date: Wed, 28 Sep 2011 21:59:19 -0400	[thread overview]
Message-ID: <20110929015919.GL19250@thunk.org> (raw)
In-Reply-To: <7vd3ekxkca.fsf@alter.siamese.dyndns.org>

On Wed, Sep 28, 2011 at 05:28:53PM -0700, Junio C Hamano wrote:
> 
> I suspect that letting GPG do the compression and shipping foo.tar.gpg
> would work just fine as well, 

Good point.  If only "tar -xW foo.tar.gpg" automatically verified the
gpg signature, that would work really well indeed.  :-)

> I understand that the automated GPG signature k.org used to use on the
> master machine was primarily to protect the copies that the mirrors serve
> from getting tampered after they leave the master machine. Do you happen
> to know what the new policy will be? Will the developers who distribute
> their snapshot tarballs from the site be GPG signing them themselves
> before uploading?

This is still being negotiated.  Given that developers are starting to
sign their release tags (and of course Linus has been doing this
already), one of the things that I've proposed is that we support is
to have the developer do something like this:

git archive --format=tar -o e2fsprogs-1.41.12.tar v1.41.12
gzip -9n e2fsprogs-1.41.12.tar
gpg --sign --detach -a e2fsprogs-1.41.12.tar.gz

and then just uploading the tar.gz.gpg file, the URL for the git tree,
and the tag that the server should use do the extraction.

> That would improve the situation (I suspect that there
> were some people who misunderstood that these GPG signature were to
> protect against break-in at the master machine), but at the same time, it
> may create the chicken-and-egg bootstrapping problem if public keys of too
> many people need to be published securely.

We are in the process of bootstrapping a GPG web of trust.  Linus has
generated a new GPG key which has been signed by Peter Anvin, Dirk,
and myself.  We'll get a much richer set of cross signatures at the
Kernel Summit in Prague in a few months.

Also, there's a pretty good intersection between kernel developers and
the Debian web of trust; there's been some talk of using that as an
auxiliary bootstrap for isolated kernel developers in distant part of
the world.

					- Ted

  reply	other threads:[~2011-09-29  1:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 23:48 Lack of detached signatures Joseph Parmelee
2011-09-28  0:03 ` Junio C Hamano
2011-09-28  0:07   ` Michael Witten
2011-09-28  4:17     ` Olsen, Alan R
2011-09-28  7:41       ` Carlos Martín Nieto
2011-09-28 12:36         ` Joseph Parmelee
2011-09-28 16:45           ` Junio C Hamano
2011-09-28 16:55             ` Michael Witten
2011-09-28 16:59             ` Matthieu Moy
2011-09-28 22:25             ` Jeff King
2011-09-28 23:09               ` Ted Ts'o
2011-09-29  0:28                 ` Junio C Hamano
2011-09-29  1:59                   ` Ted Ts'o [this message]
2011-09-29  3:50                     ` Junio C Hamano
2011-09-29 13:18                       ` Ted Ts'o
2011-09-29 14:40                         ` Sverre Rabbelier
2011-09-29 14:50                           ` Ted Ts'o
2011-09-29 14:52                             ` Sverre Rabbelier
2011-09-29 16:47                         ` Joseph Parmelee
2011-09-29  1:29                 ` Joseph Parmelee
2011-09-29  1:41                 ` Jeff King
2011-09-29 20:31                 ` Olsen, Alan R
2011-09-28 22:40             ` Joseph Parmelee
2011-09-28 17:03       ` Ben Walton

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=20110929015919.GL19250@thunk.org \
    --to=tytso@mit.edu \
    --cc=alan.r.olsen@intel.com \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jparmele@wildbear.com \
    --cc=mfwitten@gmail.com \
    --cc=peff@peff.net \
    /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.