From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH v2 0/5] Update the maintainer PGP guide
Date: Mon, 08 Aug 2022 17:31:48 -0400 [thread overview]
Message-ID: <20220727-docs-pgp-guide-v2-0-e3e6954affb6@linuxfoundation.org> (raw)
This series updates the guide to match terminology used in the upstream
"protecting code integrity" guide and brings the documentation in line
with the latest developments in the GnuPG world:
- uses "Certify key" instead of "master key" terms to remove common
confusion that the "Certify key" is somehow able to restore lost
private subkeys
- removes keyserver instructions because keyservers have largely gone
semi-extinct due to GDPR enforcement and just general neglect
- adds a link to the kernel.org PGP keyring documentation
- updates information about ECC curve support among the devices the
guide talks about (Yubikeys are able to use ED25519 curves with the
latest firmware updates)
- adds a section on using PGP-signed patches with b4 and patatt
Link: https://github.com/lfit/itpol/blob/master/protecting-code-integrity.md
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
---
Changes in v2:
- Rebase on v5.19.
- Small wording changes based on feedback.
- Link to v1: https://lore.kernel.org/r/20220727-docs-pgp-guide-v1-0-c48fb06cb9af@linuxfoundation.org
---
Konstantin Ryabitsev (5):
maintainer-pgp-guide: use key terminology consistent with upstream
maintainer-pgp-guide: remove keyserver instructions
maintainer-pgp-guide: update ECC support information
maintainer-pgp-guide: add a section on PGP-signed patches
maintainer-pgp-guide: minor wording tweaks
Documentation/process/maintainer-pgp-guide.rst | 286 ++++++++++++-------------
1 file changed, 142 insertions(+), 144 deletions(-)
---
base-commit: 3d7cb6b04c3f3115719235cc6866b10326de34cd
change-id: 20220727-docs-pgp-guide-1dfc91614c0f
Best regards,
--
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
next reply other threads:[~2022-08-08 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 21:31 Konstantin Ryabitsev [this message]
2022-08-08 21:31 ` [PATCH v2 1/5] maintainer-pgp-guide: use key terminology consistent with upstream Konstantin Ryabitsev
2022-08-08 21:31 ` [PATCH v2 2/5] maintainer-pgp-guide: remove keyserver instructions Konstantin Ryabitsev
2022-08-08 21:31 ` [PATCH v2 3/5] maintainer-pgp-guide: update ECC support information Konstantin Ryabitsev
2022-08-08 21:31 ` [PATCH v2 4/5] maintainer-pgp-guide: add a section on PGP-signed patches Konstantin Ryabitsev
2022-08-08 21:31 ` [PATCH v2 5/5] maintainer-pgp-guide: minor wording tweaks Konstantin Ryabitsev
2022-08-18 17:14 ` [PATCH v2 0/5] Update the maintainer PGP guide Jonathan Corbet
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=20220727-docs-pgp-guide-v2-0-e3e6954affb6@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=corbet@lwn.net \
--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