From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: keys@linux.kernel.org
Subject: Re: Updated key for me
Date: Tue, 13 Oct 2026 13:19:02 +0200 [thread overview]
Message-ID: <as4Rmi2qBg0ekLTV@monoceros> (raw)
In-Reply-To: <48b890a9-1f26-486e-9a32-3d20829f7db5@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Hello Mark,
On Tue, Oct 13, 2026 at 11:51:12AM +0100, Mark Brown wrote:
> On Tue, Oct 13, 2026 at 07:36:58AM +0200, Uwe Kleine-König wrote:
> > On Thu, Oct 01, 2026 at 04:05:29PM +0100, Mark Brown wrote:
> > > Attached as per https://korg.docs.kernel.org/pgpkeys.html.
> >
> > The attachment contains two certificates. A dsa1024 one from 1998 and an
> > rsa4096 from 2011. I guess only the second was intended? But that also
> > has (pre-existing) SHA1 issues, according to `sq cert lint`:
> >
> > Certificate C3F436CA30F5D8EB, key DD6A5FE57B78DB59 uses a SHA-1-protected binding signature.
> >
> > Would be great if you fixed that. If you don't know how, I'm glad to
> > help.
>
> That message does not even tell me enough to identify a problem.
It means that the proof that the encryption subkey DD6A5FE57B78DB59
belongs to your primary key is based on SHA1 instead of something that
is still considered safe for some time.
The easy fix is
sq cert lint --fix --output - --cert DD6A5FE57B78DB59 | gpg --import
(if sq can access your primary key) or (I guess) Konstantin's
rebind-modern-hash.py script (can be found in
git@gitolite.kernel.org:/pub/scm/docs/kernel/pgpkeys.git).
Or if you want to go through the deep details with GnuPG, see
https://lore.kernel.org/keys/fxotnlhsyl2frp54xtguy7ryrucuwselanazixeax3motyyoo3@7vf7ip6gxyvx/
.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-10-13 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 15:05 Updated key for me Mark Brown
2026-10-13 5:36 ` Uwe Kleine-König
2026-10-13 10:51 ` Mark Brown
2026-10-13 11:19 ` 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=as4Rmi2qBg0ekLTV@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=broonie@kernel.org \
--cc=keys@linux.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.