From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v1 2/5] maintainer-pgp-guide: remove keyserver instructions
Date: Fri, 29 Jul 2022 08:47:02 +0700 [thread overview]
Message-ID: <78f782da-1af9-a068-3aa5-1d6102f5e8c1@gmail.com> (raw)
In-Reply-To: <20220727-docs-pgp-guide-v1-2-c48fb06cb9af@linuxfoundation.org>
On 7/29/22 03:57, Konstantin Ryabitsev wrote:
> Keyservers are largely a thing of the past with the replacement systems
> like keys.openpgp.net specifically designed to offer no support for the
> web of trust. Remove all sections that talk about keyservers and add a
> small section with the link to kernel.org documentation that talks about
> using the kernel.org public key repository.
>
AFAIK, keyservers are synchronized (federated). For example, when I submit
my key to keys.openpgp.net, other keyservers (like keyserver.ubuntu.com
that I use) also gets a copy of my key. So "replacement systems" in
this case is referred to kernel.org key repository (using git). The
wording should be "Replace keyservers section with kernel.org public
key repository usage".
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-07-29 1:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 20:57 [PATCH v1 0/5] Update the maintainer PGP guide Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 1/5] maintainer-pgp-guide: use key terminology consistent with upstream Konstantin Ryabitsev
2022-07-30 13:12 ` Wu XiangCheng
2022-08-02 17:07 ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 2/5] maintainer-pgp-guide: remove keyserver instructions Konstantin Ryabitsev
2022-07-29 1:47 ` Bagas Sanjaya [this message]
2022-08-02 17:21 ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 3/5] maintainer-pgp-guide: update ECC support information Konstantin Ryabitsev
2022-07-29 9:11 ` Bagas Sanjaya
2022-08-02 17:16 ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 4/5] maintainer-pgp-guide: add a section on PGP-signed patches Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 5/5] maintainer-pgp-guide: minor wording tweaks Konstantin Ryabitsev
2022-07-29 22:55 ` Randy Dunlap
2022-08-02 17:09 ` Konstantin Ryabitsev
2022-08-02 9:07 ` [PATCH v1 0/5] Update the maintainer PGP guide Alexander Dahl
2022-08-02 17:00 ` 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=78f782da-1af9-a068-3aa5-1d6102f5e8c1@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®