All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: Alan Maguire <almagui@kernel.org>, keys@kernel.org
Subject: Re: updating key to more stable kernel.org address, revoking alan.maguire@oracle.com
Date: Tue, 3 Nov 2026 12:59:38 +0100	[thread overview]
Message-ID: <aunK1fbd06aZGrui@monoceros> (raw)
In-Reply-To: <20261030-massive-mindful-kiwi-f3ba1f@vache>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

On Fri, Oct 30, 2026 at 04:30:16PM +0000, Konstantin Ryabitsev wrote:
> On Fri, Oct 30, 2026 at 11:33 AM, Alan Maguire wrote:
> > already uploaded to openpgp, sending here too as per process. Thanks!
> 
> Hi, Alan:
> 
> Thanks! I've added your earlier update with the new expiration date, but
> not this one:
> 
> Your key's only trust path into the kernel.org keyring is Konrad Wilk's
> signature on your alan.maguire@oracle.com user ID. Revoking that user ID
> also drops his signature, and the almagui@kernel.org UID has no signatures at
> all yet, so your key would fall out of the keyring as a result.

If I look at the output of

	sq inspect --certifications < keys/8A7AECDB2E53B836.asc

there are already two signatures on the kernel.org UID. This emits two
errors, but that's due to the certificates by Konrad Rzeszutek Wilk and
Boris Ostrovsky having SHA1 issues.

These two signatures were not part of the key block in Alan's mail
though, but on my side the import still works fine.

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-11-03 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 11:33 updating key to more stable kernel.org address, revoking alan.maguire@oracle.com Alan Maguire
2026-10-30 16:30 ` Konstantin Ryabitsev
2026-11-03 11:59   ` Uwe Kleine-König [this message]

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=aunK1fbd06aZGrui@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=almagui@kernel.org \
    --cc=keys@kernel.org \
    --cc=mricon@kernel.org \
    /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.