Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 29 Jul 2022 16:11:26 +0700
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
Message-ID: <YuOkPtg+Wa7KldPm@debian.me>
References: <20220727-docs-pgp-guide-v1-0-c48fb06cb9af@linuxfoundation.org>
 <20220727-docs-pgp-guide-v1-3-c48fb06cb9af@linuxfoundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20220727-docs-pgp-guide-v1-3-c48fb06cb9af@linuxfoundation.org>
Precedence: bulk

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