From: "Greg A. Woods" <woods@planix•com>
To: The Git Mailing List <git@vger•kernel.org>
Subject: Re: PATCH: Less fragile lookup of gpg key
Date: Sun, 02 May 2010 20:59:34 -0400 [thread overview]
Message-ID: <m1O8k0Z-000kndC@most.weird.com> (raw)
In-Reply-To: <7v7hnn4cun.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
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
>
> 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/
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
next prev parent reply other threads:[~2010-05-03 0:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 15:16 PATCH: Less fragile lookup of gpg key Grant Olson
2010-05-01 16:26 ` A Large Angry SCM
2010-05-01 17:18 ` Junio C Hamano
2010-05-01 17:25 ` Grant Olson
2010-05-01 19:54 ` Junio C Hamano
2010-05-02 23:39 ` Grant Olson
2010-05-03 0:59 ` Greg A. Woods [this message]
2010-05-03 2:09 ` Grant Olson
2010-05-03 11:16 ` Theodore Tso
2010-05-03 22:19 ` Greg A. Woods
2010-05-04 2:19 ` tytso
2010-05-04 2:23 ` Grant Olson
2010-05-04 6:07 ` Andreas Ericsson
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=m1O8k0Z-000kndC@most.weird.com \
--to=woods@planix$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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