From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: keys@kernel.org, mricon@kernel.org
Subject: Re: Key Update: Janosch Frank C06352F3CBDF73DFAFE3962AE354E6B8E238B9F8 E354E6B8E238B9F8
Date: Thu, 29 Oct 2026 15:44:55 +0100 [thread overview]
Message-ID: <auNalpff5F5usT2u@monoceros> (raw)
In-Reply-To: <63d173e7-93f3-4a70-9118-4b0bbcb28424@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
On Thu, Oct 29, 2026 at 01:52:27PM +0100, Janosch Frank wrote:
> Like lots of people on the net I lost the passphrase for my old key
> 6577ED26BC0218E19722E72C170EFFC43C644579 a while ago and moved over to
> C06352F3CBDF73DFAFE3962AE354E6B8E238B9F8 / E354E6B8E238B9F8. I've used that
> key to sign my pull requests since ~2018.
>
> E354E6B8E238B9F8 already has certifications from my peer maintainers and
> developers which were added in 2018 / 2019.
>
> The key has been uploaded to openpgp as well:
> https://keys.openpgp.org/search?q=frankja%40linux.ibm.com
>
> Please change the stored key for me.
> Thanks!
> -----BEGIN PGP PUBLIC KEY BLOCK-----
>
> xsFNBFubpD4BEADX0uhkRhkj2AVn7kI4IuPY3A8xKat0ihuPDXbynUC77mNox7yv
> K3X5QBO6qLqYr+qrG3buymJJRD9xkp4mqgasHdB5WR9MhXWKH08EvtvAMkEJLnqx
> [...]
> 1gsax7HDIZKxVi4WIjxeIqYV+1DXTlgUPdKqR8gMR5g2s3aNu4BI377IGDHb3ipJ
> xDkxG+aYcMVoIOwXCA6CX/VDAg==
> =R9cN
> -----END PGP PUBLIC KEY BLOCK-----
The key looks fine. It has only a single valid signature by Martin
Schwidefsky. There are a few other signatures, but they are using SHA1
or are by folks not in the keyring and so are not considered.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-10-29 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 12:52 Key Update: Janosch Frank C06352F3CBDF73DFAFE3962AE354E6B8E238B9F8 E354E6B8E238B9F8 Janosch Frank
2026-10-29 14:44 ` 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=auNalpff5F5usT2u@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=frankja@linux.ibm.com \
--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.