git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GPG public keys

From
JEJamie Evans <jamie@pixelrebel.com>
Date
Dec 9, 2015, 17:03 UTC
Message-ID
<3860CB92-AD83-4372-AE7C-BBA8BF2D8F67@pixelrebel.com>
In-Reply-To
<xmqqtwnsie6h.fsf@gitster.mtv.corp.google.com>
Thanks, Junio, for the tutorial!  I had tried to lookup the key, but failed to put the ‘0x’ at the head.  
I was actually verifying the signature on a tarball release.  Just curious, how do I know the key in the database really belongs to you?  It’s has your name and email, but what’s to keep an imposter from creating a key with your name on it and posting it to the database?  I guess all the signatories on your key are others vouching for your key?
Thanks again for the reply.  Oh, and thanks for git! 

Cheers, Jamie

Show 61 quoted lines
> On Dec 8, 2015, at 5:49 PM, Junio C Hamano <gitster@pobox.com> wrote:
> 
> Jamie Evans <jamie@pixelrebel.com> writes:
> 
>> Can you please point me to the public GPG keys used for source code signing?
> 
> I suspect that you are asking about our project, but instead of
> throwing you a fish, I'll show you how to catch one yourself.
> 
> In a copy of linux kernel repository I have lying around from a
> random past, I did this:
> 
>    $ git log --show-signature
> 
> and saw something like this:
> 
>    commit c6fa8e6de3dc420cba092bf155b2ed25bcd537f7
>    merged tag 'arm64-fixes'
>    gpg: Signature made Wed 07 Oct 2015 03:10:34 AM PDT using RSA key ID 84C16334
>    gpg: Can't check signature: public key not found
>    Merge: e82fa92 62c6c61
>    Author: Linus Torvalds <torvalds@linux-foundation.org>
>    Date:   Wed Oct 7 18:17:46 2015 +0100
> 
>        Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/li...
> 
> I do not have the public key with key ID 84C16334, but I can ask
> public keyservers.  Put 0x84C16334 in "Search String" in pgp.mit.edu
> and click "Do the search!"--it would result in the key that was used
> to sign the merge request that resulted in this merge.
> 
> I also can do this:
> 
>    $ git tag -v v3.0
> 
> and I would see something like:
> 
>    object 02f8c6aee8df3cdc935e9bdd4f2d020306035dbe
>    type commit
>    tag v3.0
>    tagger Linus Torvalds <torvalds@linux-foundation.org> 1311301049 -0700
> 
>    Linux 3.0
> 
>    w00t!
>    gpg: Signature made Thu 21 Jul 2011 07:17:44 PM PDT using DSA key ID 76E21CBB
>    gpg: Good signature from "Linus Torvalds (tag signing key) <torvalds@osdl.org>"
>    ...
> 
> to find that Linus's tag signing key has ID 0x76E21CBB (I do have
> his key in my keyring, so this does not say "Can't check").
> 
> Perhaps you can do the same to whatever project you are interested
> in.  For example, here is a starting point to do the same for our
> recent v2.6.4 tag:
> 
>    $ git tag -v v2.6.4
>    gpg: Signature made Tue 08 Dec 2015 02:12:50 PM PST using RSA key ID 96AFE6CB
>    gpg: Can't check signature: public key not found
>    error: could not verify the tag 'v2.6.4'
> 
Previous: Junio C HamanoNext: Jeff King
Message 3 of 7 in “GPG public keys”
  1. Jamie EvansDec 8, 2015
  2. Junio C HamanoDec 9, 2015
  3. Jamie EvansDec 9, 2015
  4. Jeff KingDec 9, 2015
  5. Stefan BellerDec 9, 2015
  6. Jeff KingDec 9, 2015
  7. brian m. carlsonDec 10, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.