From: SJ Park <sj@kernel.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: SJ Park <sj@kernel.org>, keys@kernel.org
Subject: Re: Updated GPG key for sj (was: "Re: Your kernel.org PGP key has conflicting expiration dates")
Date: Wed, 28 Oct 2026 20:20:51 -0700 [thread overview]
Message-ID: <20261029032052.174414-1-sj@kernel.org> (raw)
In-Reply-To: <20261028-industrious-sage-piculet-0b2a35@lemur>
On Wed, 28 Oct 2026 22:45:54 -0400 Konstantin Ryabitsev <mricon@kernel.org> wrote:
> On Wed, Oct 28, 2026 at 04:57:46PM -0700, SJ Park wrote:
> > Attching the updated key below. Note that I use "SJ Park" as my name for kernel
> > development now, so modified your above command to use that.
> >
> > Please let me know if I did anything wrong.
>
> Looks good, but... while I have you! Could you please run this script to
> strengthen all the signatures on the keys you've signed in the past?
>
> https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/plain/scripts/resign-modern-hash.py
>
> The instructions are in the header. That should help improve the web of trust
> in the keyring.
Thank you for sharing this! I ran the script, and seems no action is needed
from my side.
'''
pgpkeys$ git checkout origin/master
[...]
HEAD is now at 10e606b8 Restore expired keys removed in 2025 to keys/expired/
$ ./scripts/resign-modern-hash.py
Certifier: B84722821233BD43B8D0922B8BC68E994040912F
Keys dir: /home/lkhack/pgpkeys/keys
Building analysis keyring... 649 keys.
Cross-checking local keyring... 1 matching key.
[ OK ] 7967F76ABB41FC44 SHA512 Namhyung Kim <namhyung@kernel.org>
[ OK ] FF18FCC1C43759F3 SHA256 Minchan Kim <minchan@kernel.org>
[ OK ] 7E271B2ACD1D430D SHA512 Puranjay Mohan <puranjay@kernel.org>
[ OK ] 5A0312EB0C1DEAE3 SHA512 Harry Yoo <harry@kernel.org>
All your certifications in pgpkeys.git and your local keyring use modern hash algorithms.
This only covers your signatures on other people's keys. To check
your own key's self-signatures, run:
scripts/rebind-modern-hash.py --fpr B84722821233BD43B8D0922B8BC68E994040912F
pgpkeys$ ./scripts/resign-modern-hash.py --signer B84722821233BD43B8D0922B8BC68E994040912F
Certifier: B84722821233BD43B8D0922B8BC68E994040912F
Keys dir: /home/lkhack/pgpkeys/keys
Building analysis keyring... 649 keys.
Cross-checking local keyring... 1 matching key.
[ OK ] 7967F76ABB41FC44 SHA512 Namhyung Kim <namhyung@kernel.org>
[ OK ] FF18FCC1C43759F3 SHA256 Minchan Kim <minchan@kernel.org>
[ OK ] 7E271B2ACD1D430D SHA512 Puranjay Mohan <puranjay@kernel.org>
[ OK ] 5A0312EB0C1DEAE3 SHA512 Harry Yoo <harry@kernel.org>
All your certifications in pgpkeys.git and your local keyring use modern hash algorithms.
This only covers your signatures on other people's keys. To check
your own key's self-signatures, run:
scripts/rebind-modern-hash.py --fpr B84722821233BD43B8D0922B8BC68E994040912F
pgpkeys$ ./scripts/resign-modern-hash.py --verify
Certifier: B84722821233BD43B8D0922B8BC68E994040912F
Keys dir: /home/lkhack/pgpkeys/keys
Building analysis keyring... 649 keys.
Cross-checking local keyring... 1 matching key.
[ OK ] 7967F76ABB41FC44 SHA512 Namhyung Kim <namhyung@kernel.org>
[ OK ] FF18FCC1C43759F3 SHA256 Minchan Kim <minchan@kernel.org>
[ OK ] 7E271B2ACD1D430D SHA512 Puranjay Mohan <puranjay@kernel.org>
[ OK ] 5A0312EB0C1DEAE3 SHA512 Harry Yoo <harry@kernel.org>
All your certifications in pgpkeys.git and your local keyring use modern hash algorithms.
This only covers your signatures on other people's keys. To check
your own key's self-signatures, run:
scripts/rebind-modern-hash.py --fpr B84722821233BD43B8D0922B8BC68E994040912F
'''
Please let me know if I missed something.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-10-29 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261028-otter-of-theoretical-revolution-f1ef8d@vache>
2026-10-28 23:57 ` Updated GPG key for sj (was: "Re: Your kernel.org PGP key has conflicting expiration dates") SJ Park
2026-10-29 2:45 ` Konstantin Ryabitsev
2026-10-29 3:20 ` SJ Park [this message]
2026-10-29 3:35 ` 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=20261029032052.174414-1-sj@kernel.org \
--to=sj@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.