All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: keys@linux.kernel.org
Subject: Re: Replacement GPG key for Sasha Levin
Date: Wed, 25 Mar 2026 13:23:28 -0400	[thread overview]
Message-ID: <acQaELvVL7aF5Oc_@laps> (raw)
In-Reply-To: <acN9F9hCGUliPkQh@monoceros>

On Wed, Mar 25, 2026 at 07:28:40AM +0100, Uwe Kleine-König wrote:
>Hello Sasha,
>
>On Tue, Mar 24, 2026 at 08:49:53PM -0400, Sasha Levin wrote:
>> Please add my new ed25519 GPG key to the keyring, replacing my old RSA-4096 key
>> (E27E5D8A3403A2EF66873BBCDEA66FF797772CDC).
>
>In contrast to the old certificate the new one makes `sq cert lint`
>happy, so that's a good step. (The old one resulted in
>	Certificate DEA66FF797772CDC contains a User ID (Sasha Levin <alexander.levin@verizon.com>) protected by SHA-1
>	Certificate DEA66FF797772CDC contains a User ID (Sasha Levin <sasha.levin@oracle.com>) protected by SHA-1
>	Certificate DEA66FF797772CDC, key D0065D755EB09DBB uses a SHA-1-protected binding signature.
>.)
>
>> The new key is cross-signed by the old one.
>
>The old cert only has a single trust path (see
>https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/plain/graphs/DEA66FF797772CDC.svg),
>as the new cert is only signed by the old, it also only has a single path
>through the old one. It would be great to improve that, still because
>that single path goes away when the old cert is removed.

Ugh... I thought I had a few more signatures there.

Thanks for pointing it out. Looks like I need to ask a few folks for signatures
during LPC/LSF :)

-- 
Thanks,
Sasha

  reply	other threads:[~2026-03-25 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25  0:49 Replacement GPG key for Sasha Levin Sasha Levin
2026-03-25  6:28 ` Uwe Kleine-König
2026-03-25 17:23   ` Sasha Levin [this message]
2026-03-26 19:46 ` Konstantin Ryabitsev

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=acQaELvVL7aF5Oc_@laps \
    --to=sashal@kernel.org \
    --cc=keys@linux.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.