gpg: can't handle public key algorithm 18

[Mike Schleif]

Yes, I see that.

However, our public key was generated by our GPG; and this file is
encrypted with our public key, since there is NO missing "secret key" error.

Why, then, the subject error message?


On Sat, Apr 15, 2023 at 3:37 PM Todd Zullinger via Gnupg-users <
gnupg-users at gnupg.org> wrote:

> Mike Schleif wrote:
> > $ gpg --version
> > gpg (GnuPG) 2.0.22
> > libgcrypt 1.5.3
> >
> > $ cat /etc/system-release
> > CentOS Linux release 7.9.2009 (Core)
>
> Algorithm 18 is ECDH, which is not supported by gpg on
> CentOS 7.  You can confirm this in the Pubkey line of the
> gpg --version output:
>
>   $ gpg --version
>   gpg (GnuPG) 2.0.22
>   libgcrypt 1.5.3
>   [...]
>
>   Home: ~/.gnupg
>   Supported algorithms:
>   Pubkey: RSA, ?, ?, ELG, DSA
>   Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
>           CAMELLIA128, CAMELLIA192, CAMELLIA256
>   Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
>   Compression: Uncompressed, ZIP, ZLIB, BZIP2
>
> On a newer Fedora system, ECDH is present:
>
>   $ gpg --version --no-copyright
>   gpg (GnuPG) 2.4.0
>   libgcrypt 1.10.1-unknown
>   [...]
>
>   Home: /home/user/.gnupg
>   Supported algorithms:
>   Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
>   Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
>           CAMELLIA128, CAMELLIA192, CAMELLIA256
>   Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
>   Compression: Uncompressed, ZIP, ZLIB, BZIP2
>
> --
> Todd
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> https://lists.gnupg.org/mailman/listinfo/gnupg-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20230416/d7e20e05/attachment.html>