From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Will Deacon <will@kernel.org>
Cc: keys@linux.kernel.org
Subject: Re: will@kernel.org
Date: Fri, 24 Jul 2026 19:59:29 +0200 [thread overview]
Message-ID: <amOm00f_J8bZFw_f@monoceros> (raw)
In-Reply-To: <amNtKaEO-HMnhrYE@willie-the-truck>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
Hello Will,
On Fri, Jul 24, 2026 at 02:48:25PM +0100, Will Deacon wrote:
> -----BEGIN PGP PUBLIC KEY BLOCK-----
>
> mQINBE6G5s0BEADDGfOcthrGJKfkcrFBdCyduDIsx7Ca02KKtvuNsBrpj5mDGSlf
> [...]
> LFYBaYx/l+Gxzd10OVv2br/umTyBkQB59JlclrCcW7RYl5jbBO0P+PKfTVWV
> =FO5n
> -----END PGP PUBLIC KEY BLOCK-----
`sq cert lint` reports:
Certificate 2DFBF4523E542FD9, key 4687FCE0E1EAD0C4 uses a SHA-1-protected binding signature.
I think the script by Konstantin (used to redo all the old signatures
also suffering from using SHA1). If not, `sq cert lint --fix` is the
easiest way to fix that.
Also one of your identities uses a UID comment. See
https://dkg.fifthhorseman.net/blog/openpgp-user-id-comments-considered-harmful.html
for learning why this is bad.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-07-24 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 13:48 will@kernel.org Will Deacon
2026-07-24 17:59 ` Uwe Kleine-König [this message]
2026-07-26 11:31 ` will@kernel.org Will Deacon
2026-10-23 9:12 ` will@kernel.org Uwe Kleine-König
-- strict thread matches above, loose matches on Subject: below --
2021-08-09 12:11 will@kernel.org Will Deacon
2021-08-09 15:17 ` will@kernel.org 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=amOm00f_J8bZFw_f@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=keys@linux.kernel.org \
--cc=will@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.