workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: update maintainer-pgp-guide for latest best practices
Date: Wed, 03 Sep 2025 09:37:28 +0100	[thread overview]
Message-ID: <9fbb364c46d4affdadec7702c4c0e8987f7dae03.camel@pbarker.dev> (raw)
In-Reply-To: <20250902-pgp-guide-updates-v1-1-62ac7312d3f9@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

On Tue, 2025-09-02 at 11:44 -0400, Konstantin Ryabitsev wrote:
> Freshen up the maintainer PGP guide:
> 
> - Bump minimum GnuPG version requirement from 2.2 to 2.4, since 2.2 is
>   no longer maintained
> - All major hardware tokens now support Curve25519, so remove outdated
>   ECC support callouts
> - Update hardware device recommendations (Nitrokey Pro 2 -> Nitrokey 3)
> - Broaden backup media terminology (USB thumb drive -> external media)
> - Update wording to follow vale's linter recommendations
> - Various minor wording improvements for clarity
> 
> Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>

In the last couple of months I moved my private keys onto a new Yubikey device,
mostly following the kernel maintainer PGP guide. I read through the guide, and
some other sources [1] [2] [3], in detail before I started. So I think I'm well
placed to review these changes. They LGTM!

Reviewed-by: Paul Barker <paul@pbarker.dev>

[1]: https://github.com/drduh/YubiKey-Guide
[2]: https://support.yubico.com/hc/en-us/articles/360013790259-Using-Your-YubiKey-with-OpenPGP
[3]: https://github.com/lfit/itpol/blob/master/protecting-code-integrity.md

-- 
Paul Barker

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2025-09-03  8:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 15:44 [PATCH] Documentation: update maintainer-pgp-guide for latest best practices Konstantin Ryabitsev
2025-09-03  8:37 ` Paul Barker [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=9fbb364c46d4affdadec7702c4c0e8987f7dae03.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=corbet@lwn.net \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=workflows@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;
as well as URLs for NNTP newsgroup(s).