From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: keys@linux.kernel.org
Subject: Re: key for u.kleine-koenig@pengutronix.de
Date: Fri, 24 Mar 2023 11:35:08 -0400 [thread overview]
Message-ID: <hcfu4f737lrc4hdq42axtb2bscf3zmpesvxo5ynpd2ilcrgsvd@b7oozol5zugk> (raw)
In-Reply-To: <20230313180127.nz2rwcces2q3gds5@pengutronix.de>
On Mon, Mar 13, 2023 at 07:01:27PM +0100, Uwe Kleine-König wrote:
> .keyring/openpgp/kleine-knig.de/uwe/default
>
> I don't know how this .keyring directory is used but I wonder about
> the "kleine-knig.de" part. The (nearly) matching uid for that is
>
> Uwe Kleine-König <uwe@kleine-könig.de>
>
> . In transit this is usually encoded using puny-code which would make
> that
>
> uwe@xn--kleine-knig-yfb.de
>
> . So I wouldn't have been surprised if there was a file named
>
> .keyring/openpgp/kleine-könig.de/uwe/default
>
> or
>
> .keyring/openpgp/xn--kleine-knig-yfb.de/uwe/default
>
> but the filename above looks wrong.
You're right, it's a bug in the code that tries to be extra-safe when creating
dirnames. The .keyring contents can be used with b4, but not very many people
do, so the impact of this is tiny to minimal and benign (your key simply won't
be properly found).
Thank you for the report -- I'll try to fix the bug next time I'm poking at
the pgpkeys generation code.
-K
prev parent reply other threads:[~2023-03-24 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 9:54 key for u.kleine-koenig@pengutronix.de Uwe Kleine-König
2022-06-10 17:13 ` Konstantin Ryabitsev
2023-03-13 18:01 ` Uwe Kleine-König
2023-03-24 15:35 ` Konstantin Ryabitsev [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=hcfu4f737lrc4hdq42axtb2bscf3zmpesvxo5ynpd2ilcrgsvd@b7oozol5zugk \
--to=konstantin@linuxfoundation.org \
--cc=keys@linux.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).