lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YuOkPtg+Wa7KldPm@debian.me>
Date:   Fri, 29 Jul 2022 16:11:26 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH v1 3/5] maintainer-pgp-guide: update ECC support
 information

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ