Baptiste,
usually the bit length of the characteristic /p /of the finite field,
where all the coordinate computationa are made, is taken as the key
length. And whereas this bit length of the prime for the NIST curve
P-256 is 256 , it is 255 for Curve25519. Therefore the key length value
is
On Freitag, 17. September 2021 13:36:48 CEST Johan Wevers via Gnupg-users
wrote:
> On 16-09-2021 12:27, Werner Koch wrote:
> > https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.31_202109.exe.sig
>
> The signature file can't be found.
On 16-09-2021 12:27, Werner Koch wrote:
>
On 16-09-2021 12:27, Werner Koch wrote:
> https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.31_202109.exe.sig
The signature file can't be found.
--
ir. J.C.A. Wevers
PGP/GPG public keys at http://www.xs4all.nl/~johanw/pgpkeys.html
___
Gnupg-users
Hi Eric,
Am Mittwoch 04 August 2021 19:58:49 schrieb Eric Y. Lin:
> I've built up a win32 application to remotely import a public key to verify
> a digital signature. Everything works fine in a Windows 10 machine. Yet, as
> I was trying this win32 app when the gpg4win-3.1.16 was uninstalled, it
>
Baptiste Beauplat wrote:
> I noticed that the key size reported by gpg --with-colons for ECC keys
> (ed25519) have changed from 256 to 255.
Thank you for sharing. I didn't know that it is exposed to users.
(I considered it were (only) internal thing in libgcrypt.)
> I was wondering if that's a
