From: Jonathan McDowell <noodles@earth.li>
To: konstantin@linuxfoundation.org
Cc: Matthew Wilcox <willy@infradead.org>,
Oliver Graute <oliver.graute@gmail.com>,
corbet@lwn.net, miguel.ojeda.sandonis@gmail.com,
grandmaster@al2klimov.de, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: PGP pathfinder service is no longer maintained
Date: Thu, 17 Dec 2020 19:25:56 +0000 [thread overview]
Message-ID: <20201217192555.GA17262@earth.li> (raw)
In-Reply-To: <20201216224344.h3r7wbo7fgatupm5@chatter.i7.local>
In article <20201216224344.h3r7wbo7fgatupm5@chatter.i7.local> (earth.lists.linux-kernel) you wrote:
> On Wed, Dec 16, 2020 at 10:20:18PM +0000, Matthew Wilcox wrote:
> > > Unfortunately the site https://pgp.cs.uu.nl/ is not maintained
> > > anymore
> > > and the "Finding paths to Linus" link in the Kernel Maintainer PGP guide
> > > is dead. Is there any alternative sites to find a way through the web of
> > > trust?
> >
> > Several. Konstantin has a local one: https://github.com/mricon/wotmate
> This is how we generate these:
> https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/tree/graphs
> > and if you want a web service, I like this one:
> > https://the.earth.li/~noodles/pathfind.html
> FYI, it says "The pathfinder is currently out of action due to queries
> taking far too long to respond. It may return in the future when I find
> enough time to optimize it." :)
I've re-enabled it for the moment; the keyserver now only holds keys it
has paths to so hopefully it'll be a bit better behaved now.
J.
--
Give me liberty or I will cut you.
prev parent reply other threads:[~2020-12-17 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 22:01 PGP pathfinder service is no longer maintained Oliver Graute
2020-12-16 22:20 ` Matthew Wilcox
2020-12-16 22:43 ` Konstantin Ryabitsev
2020-12-17 19:25 ` Jonathan McDowell [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=20201217192555.GA17262@earth.li \
--to=noodles@earth.li \
--cc=corbet@lwn.net \
--cc=grandmaster@al2klimov.de \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=oliver.graute@gmail.com \
--cc=willy@infradead.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 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 NNTP newsgroup(s).