From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: "'Sean Allred'" <allred.sean@gmail.com>,
"'Philip Oakley'" <philipoakley@iee.email>, <git@vger.kernel.org>,
<sallred@epic.com>, <grmason@epic.com>, <sconrad@epic.com>
Subject: Re: Dealing with corporate email recycling
Date: Mon, 14 Mar 2022 00:19:30 +0000 [thread overview]
Message-ID: <xmqqlexdtmgd.fsf@gitster.g> (raw)
In-Reply-To: <021401d83731$62813630$2783a290$@nexbridge.com> (rsbecker@nexbridge.com's message of "Sun, 13 Mar 2022 19:23:38 -0400")
<rsbecker@nexbridge.com> writes:
> Could we not use SSH's ssh-keygen -V for this purpose when establishing
> persistent identities independent of user/email? We already do this for
> signed commits.
Fingerprint of cryptographic key would be easy to use as an
identity, for which the person who claims ownership can easily
produce proof of ownership. Various other "identitying strings"
like human readable name and e-mail addresses from different
validity periods can be all tied to such an identity. Taking key
revocation into account, keys from different validity period may
have to be tied together in a same way. "The person who used to
sign the commits with key A and the person who signs the commits
with key B are the same, and in real life, they are known as
A. U. Thor"
But proving that such a mapping is in a meaningful way is much
harder, I would imagine, but perhaps addresses and human readable
names do not matter as much. Or continuity of identity, for that
matter. I dunno.
next prev parent reply other threads:[~2022-03-14 0:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 22:38 Dealing with corporate email recycling Sean Allred
2022-03-13 0:03 ` Junio C Hamano
2022-03-13 0:26 ` rsbecker
2022-03-13 14:01 ` Sean Allred
2022-03-13 14:20 ` rsbecker
2022-03-13 14:41 ` Sean Allred
2022-03-13 15:02 ` rsbecker
2022-03-13 15:21 ` Sean Allred
2022-03-13 19:57 ` Philip Oakley
2022-03-13 22:40 ` Sean Allred
2022-03-13 23:16 ` Junio C Hamano
2022-03-13 23:23 ` rsbecker
2022-03-14 0:19 ` Junio C Hamano [this message]
2022-03-14 11:56 ` Philip Oakley
2022-03-14 21:24 ` Junio C Hamano
2022-03-14 22:25 ` Philip Oakley
2022-03-15 1:23 ` Sean Allred
2022-03-15 11:15 ` Philip Oakley
2022-03-13 12:20 ` Philip Oakley
2022-03-13 13:35 ` Sean Allred
2022-03-14 11:59 ` Philip Oakley
2022-03-13 15:51 ` Ævar Arnfjörð Bjarmason
2022-03-13 17:22 ` brian m. carlson
2022-03-13 17:52 ` rsbecker
2022-03-13 19:47 ` rsbecker
2022-03-13 22:23 ` Sean Allred
2022-03-15 1:27 ` Sean Allred
2022-03-18 21:22 ` Peter Krefting
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=xmqqlexdtmgd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=allred.sean@gmail.com \
--cc=git@vger.kernel.org \
--cc=grmason@epic.com \
--cc=philipoakley@iee.email \
--cc=rsbecker@nexbridge.com \
--cc=sallred@epic.com \
--cc=sconrad@epic.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).