From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: lpcosse-keysigning@baylibre.com
Cc: users@linux.kernel.org, linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: PGP keysigning at LPC/OSSE 2026
Date: Tue, 4 Aug 2026 23:28:18 +0200 [thread overview]
Message-ID: <anJX1Pni94L_bMu8@monoceros> (raw)
In-Reply-To: <lpcosse2026-keysigning@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
Hello,
On Tue, Aug 04, 2026 at 05:43:43PM +0200, Uwe Kleine-König wrote:
> - 654 certificates, among them 12 invalid
> - 8088 signatures, 3613 of them invalid
> - 9 certificates are not reachable from Greg's stable key
> (38DBBDC86092693E).
> - 317 certificates are not reachable from Linus's cert
> (79BE3E4300411886). (That's why Greg is used as trust root since some
> time.)
> - strong set size: 289
> - average distance in the strong set: 4.85
> - maximal distance in the strong set: 13
> - Best connected certificate is Daniel Wagner's 587C5ECA5D0A306C which
> can reach the other strong set certs with an average of 3.89 steps.
I just noticed that the strong set facts were created with the SHA1
stuff that is still in the pgpkeys repo. With these dropped the
statistic looks as follows:
- 410 certs are not reachable from Linus's cert
- 148 certs are not reachable from Greg
- strong set size: 152
- average distance: 4.07
- maximal distance: 12
- Best connected certificate is Greg's 38DBBDC86092693E which can reach
the other certs with an average of 3.08 steps.
So hopefully the keysigning improves the situation ...
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-08-04 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 15:43 PGP keysigning at LPC/OSSE 2026 Uwe Kleine-König
2026-08-04 21:28 ` Uwe Kleine-König [this message]
2026-08-05 6:32 ` Krzysztof Kozlowski
2026-08-05 10:29 ` Uwe Kleine-König
2026-08-06 10:11 ` Krzysztof Kozlowski
2026-08-06 15:59 ` Uwe Kleine-König
2026-08-06 16:57 ` [workflows]PGP " Steven Rostedt
2026-08-06 22:15 ` Uwe Kleine-König
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=anJX1Pni94L_bMu8@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpcosse-keysigning@baylibre.com \
--cc=users@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.