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, 23 Oct 2026 11:12:49 +0200 [thread overview]
Message-ID: <atskGlwV_Zp4fxPy@monoceros> (raw)
In-Reply-To: <amXv_ez4FAu6jmXc@willie-the-truck>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Hello Will,
On Sun, Jul 26, 2026 at 12:31:09PM +0100, Will Deacon wrote:
> On Fri, Jul 24, 2026 at 07:59:29PM +0200, Uwe Kleine-König wrote:
> > 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.
>
> I'm not sure what I can do about that, but at least this appears to fall
> into the "unnecessary" case from that link. I could revoke the UID (I no
> longer have access to my @arm.com address), but I vaguely remember that
> was also not a good idea?
IMHO you should revoke it. You're losing the signatures, but your
remaining UIDs are signed well enough, so that should be OK. Other than
that I'm not aware of bad side effects, i.e. all the signatures done
with your key are still considered valid.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-10-23 9:12 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 ` will@kernel.org Uwe Kleine-König
2026-07-26 11:31 ` will@kernel.org Will Deacon
2026-10-23 9:12 ` Uwe Kleine-König [this message]
-- 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=atskGlwV_Zp4fxPy@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.