public inbox for keys@kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	keys@linux.kernel.org
Subject: Re: Update key expiration date for tytso@mit.edu
Date: Fri, 11 Apr 2025 11:01:53 -0400	[thread overview]
Message-ID: <20250411150153.GB648081@mit.edu> (raw)
In-Reply-To: <sgntx3uys3zayto7jczmbmixlvqnlqoi7fdhyrbf5sszg2wjlf@nigvacgc2v52>

On Thu, Apr 10, 2025 at 05:40:28PM +0200, Uwe Kleine-König wrote:
> On Thu, Apr 10, 2025 at 10:43:14AM -0400, Konstantin Ryabitsev wrote:
> > On Thu, Apr 10, 2025 at 10:34:55AM -0400, Theodore Ts'o wrote:
> > 
> > Updated, thanks.
> 
> This is rather odd. The commit you created indeed updated the expiry
> date on the key, but it also dropped lots of signatures. If I repeat
> importing Theodore's key, the keys are not dropped for me. (And that's
> even though I use a gpg version that is affected by
> https://dev.gnupg.org/T7583.)
> 
> The graph before the import was just "Linus -> tytso", now it's
> https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/plain/graphs/D36F769BC11804F0.svg?id=3dab90be2abbe5e36edbad698070ff390ea3f886

Yeah, that's a ltitle unfortunate, since I was originally one of the
initial 4 "trusted introducers" when we were setting up the kernel
keyring.  So dropping the signatures might affect some folks being
considered trusted by some GPG configs.  I imagine that's much less
important these days, though....

							- Ted

  reply	other threads:[~2025-04-11 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 14:34 Update key expiration date for tytso@mit.edu Theodore Ts'o
2025-04-10 14:43 ` Konstantin Ryabitsev
2025-04-10 15:40   ` Uwe Kleine-König
2025-04-11 15:01     ` Theodore Ts'o [this message]
2025-04-12  6:47       ` Uwe Kleine-König
2025-04-11 21:17     ` Konstantin Ryabitsev
2025-04-12  7:50       ` Uwe Kleine-König

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=20250411150153.GB648081@mit.edu \
    --to=tytso@mit.edu \
    --cc=keys@linux.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=u.kleine-koenig@baylibre.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