From: Jeff King <peff@peff.net>
To: Stefan Beller <sbeller@google.com>
Cc: Jamie Evans <jamie@pixelrebel.com>,
Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: GPG public keys
Date: Wed, 9 Dec 2015 17:43:36 -0500 [thread overview]
Message-ID: <20151209224335.GB32104@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGZ79kYk0RkwNj2aX6iixGjceKVYTy24os_Xb_wY8BWDZwY+Fg@mail.gmail.com>
On Wed, Dec 09, 2015 at 02:24:17PM -0800, Stefan Beller wrote:
> On Wed, Dec 9, 2015 at 2:04 PM, Jeff King <peff@peff.net> wrote:
> >
> > Of course you can't just fetch the v1.7.1.4 tag _now_, because the same
> > person impersonating the most recent tag could also be impersonating
> > (and back-dating) the older tags. But you could fetch it now, store it
> > somewhere trusted (e.g., on your laptop), and wait two weeks. If you
> > find no public outcry over hacked git, then it is probably OK to assume
> > that is the real key.
> >
>
> With all of us pointing out 96AFE6CB being the right hash, you may or may not
> trust the list enough to also trust the key now.
Who's to assume that I actually checked that 96AFE6CB is right? ;)
Actually, I don't typically verify Junio's tag signatures. I fetch and
run "make" daily, far more often than he signs, so I would have been
p0wned long ago.
-Peff
next prev parent reply other threads:[~2015-12-09 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 19:10 GPG public keys Jamie Evans
2015-12-09 1:49 ` Junio C Hamano
2015-12-09 17:03 ` Jamie Evans
2015-12-09 22:04 ` Jeff King
2015-12-09 22:24 ` Stefan Beller
2015-12-09 22:43 ` Jeff King [this message]
2015-12-10 1:16 ` brian m. carlson
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=20151209224335.GB32104@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jamie@pixelrebel.com \
--cc=sbeller@google.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).