From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v1 3/5] maintainer-pgp-guide: update ECC support information
Date: Fri, 29 Jul 2022 16:11:26 +0700 [thread overview]
Message-ID: <YuOkPtg+Wa7KldPm@debian.me> (raw)
In-Reply-To: <20220727-docs-pgp-guide-v1-3-c48fb06cb9af@linuxfoundation.org>
On Thu, Jul 28, 2022 at 04:57:06PM -0400, Konstantin Ryabitsev wrote:
>
> - If for some reason you prefer to stay with RSA subkeys, just replace
> - "ed25519" with "rsa2048" in the above command. Additionally, if you
> - plan to use a hardware device that does not support ED25519 ECC
> - keys, like Nitrokey Pro or a Yubikey, then you should use
> - "nistp256" instead or "ed25519."
> + Note, that if you plan to use a hardware device that does not
> + support ED25519 ECC keys, you should choose "nistp256" instead or
> + "ed25519."
>
nistp256 isn't just ECC key algo other than ed25519. In fact, it is a
part of NIST curve family (the others are nistp384 and nistp521).
Maybe we can just say "If unsure, or if your hardware device does not
support ED25519, use one of NIST curves (nistp256, nistp384, or nistp521)
instead".
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-07-29 9:11 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
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 [this message]
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=YuOkPtg+Wa7KldPm@debian.me \
--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;
as well as URLs for NNTP newsgroup(s).