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

Re: PATCH: Less fragile lookup of gpg key

From
GWGreg A. Woods <woods@planix.com>
Date
May 3, 2010, 00:59 UTC
Message-ID
<m1O8k0Z-000kndC@most.weird.com>
In-Reply-To
<7v7hnn4cun.fsf@alter.siamese.dyndns.org>
At Sat, 01 May 2010 12:54:24 -0700, Junio C Hamano <gitster@pobox.com> wrote:
Subject: Re: PATCH:  Less fragile lookup of gpg key
Show 5 quoted lines
> 
> If I have two keys like these:
> 
>     Junio C Hamano <gitster@pobox.com>
>     Junio Hamano <gitster@pobox.com>

I'm not an expert on PGP internals or such, but I think that's a really bad thing to do. I'm surprised you were able to get gpg to do it in the first place. I would have hoped it wouldn't allow it. As far as I can tell it's _not_ compatible with other implementations of PGP.

PGP keys normally are searched by the e-mail portion only. All the other stuff (comments and the display name, etc.) is for decoration only. This is just as it is in e-mail routing too of course.

You can of course have more than one e-mail address per key, but you should NEVER have more than one key per e-mail.

I.e. it's less reliable in the first place to have two different keys which can be found using the same e-mail address.

-- 
						Greg A. Woods
						Planix, Inc.

<woods@planix.com>       +1 416 218 0099        http://www.planix.com/
Previous: Grant OlsonNext: Grant Olson
Message 7 of 13 in “PATCH: Less fragile lookup of gpg key”
  1. Grant OlsonMay 1, 2010
  2. A Large Angry SCMMay 1, 2010
  3. Junio C HamanoMay 1, 2010
  4. Grant OlsonMay 1, 2010
  5. Junio C HamanoMay 1, 2010
  6. Grant OlsonMay 2, 2010
  7. Greg A. WoodsMay 3, 2010
  8. Grant OlsonMay 3, 2010
  9. Theodore TsoMay 3, 2010
  10. Greg A. WoodsMay 3, 2010
  11. tytso@mit.eduMay 4, 2010
  12. Grant OlsonMay 4, 2010
  13. Andreas EricssonMay 4, 2010

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.