From: Konstantin Ryabitsev <mricon@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: keys@linux.kernel.org
Subject: Re: [PATCH 0/3] b4 keyring maintenance
Date: Fri, 13 Feb 2026 16:47:03 -0500 [thread overview]
Message-ID: <20260213-bizarre-nippy-wildcat-60dd35@lemur> (raw)
In-Reply-To: <cover.1770141846.git.u.kleine-koenig@baylibre.com>
On Tue, Feb 03, 2026 at 07:19:23PM +0100, Uwe Kleine-König wrote:
> last week I noticed that there are several symlinks in .keyring (i.e.
> the directory that can be used with b4) that are not up to date. This
> patch set cleans up a part of the issues.
Merged, thank you!
> What is still open and ugly:
>
> - The scripts don't cope for these cases, so unless some manual care is
> applied, the keyring will become outdated again.
> - There are quite some email addresses that are part of two keys
> (`iconv -f latin1 keys/*.asc | sed -nr 's/^uid[^<]*<([^>]*)>/\1/p' | sort | uniq -d`
> produces some false positives)
> For these the cert that is linked to is not chosen deterministically.
I agree, this was never really completed, largely because the b4 keyring isn't
fully completed as far as designing it goes. I hope to get back to it soon,
though.
Thanks,
-K
prev parent reply other threads:[~2026-02-13 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 18:19 [PATCH 0/3] b4 keyring maintenance Uwe Kleine-König
2026-02-03 18:19 ` [PATCH 1/3] korg-update-pgpkeys: Pass --gen-b4-keyring to wotmate's export-keyring.py Uwe Kleine-König
2026-02-03 18:19 ` [PATCH 2/3] Drop broken symlinks from b4 keyring Uwe Kleine-König
2026-02-03 18:19 ` [PATCH 3/3] Drop revoked UIDs " Uwe Kleine-König
2026-02-13 21:47 ` 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=20260213-bizarre-nippy-wildcat-60dd35@lemur \
--to=mricon@kernel.org \
--cc=keys@linux.kernel.org \
--cc=u.kleine-koenig@baylibre.com \
/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