Re: gpg: can't handle public key algorithm 18

2023-04-17 Thread Konstantin Ryabitsev via Gnupg-users
On Mon, Apr 17, 2023 at 03:22:42PM +0200, Werner Koch via Gnupg-users wrote:
> >> > gpg (GnuPG) 2.0.22
> 
> That version reached end-of-life more than 5 years ago.  Don't use it.

If you need a newer version of GnuPG for RHEL7 systems, you can install
gnupg24-static from this COPR:

https://copr.fedorainfracloud.org/coprs/icon/lfit/packages/

-K

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: gpg: can't handle public key algorithm 18

2023-04-17 Thread Werner Koch via Gnupg-users
On Sun, 16 Apr 2023 10:12, Mike Schleif said:

>> > gpg (GnuPG) 2.0.22

That version reached end-of-life more than 5 years ago.  Don't use it.

>>   $ gpg --version --no-copyright

--no-copyright - There is no such option.  What you meant was
--no-greeting.
 

Salam-Shalom,

   Werner
 
-- 
The pioneers of a warless world are the youth that
refuse military service. - A. Einstein


openpgp-digital-signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: gpg: can't handle public key algorithm 18

2023-04-16 Thread Todd Zullinger via Gnupg-users
Mike Schleif wrote:
> 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?

Perhaps the file is signed by an ECDH key?  I can only
guess.

You might want to try the --list-packets option on the
encrypted message.  Adding -v (or -vv) when decrypting might
help show the issue.

-- 
Todd


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: gpg: can't handle public key algorithm 18

2023-04-16 Thread 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@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@gnupg.org
> https://lists.gnupg.org/mailman/listinfo/gnupg-users
>
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: gpg: can't handle public key algorithm 18

2023-04-15 Thread Todd Zullinger via Gnupg-users
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


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: gpg: can't handle public key algorithm 18

2023-04-15 Thread Bruce Walzer
On Sat, Apr 15, 2023 at 11:17:31AM -0500, Mike Schleif wrote:
> On trying to decrypt a file, we get the subject error on failure.

What version of GnuPG are you using? Running on what platform?

Bruce

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: gpg: can't handle public key algorithm 18

2023-04-15 Thread Mike Schleif
$ gpg --version
gpg (GnuPG) 2.0.22
libgcrypt 1.5.3

$ cat /etc/system-release
CentOS Linux release 7.9.2009 (Core)


On Sat, Apr 15, 2023 at 1:36 PM Bruce Walzer  wrote:

> On Sat, Apr 15, 2023 at 11:17:31AM -0500, Mike Schleif wrote:
> > On trying to decrypt a file, we get the subject error on failure.
>
> What version of GnuPG are you using? Running on what platform?
>
> Bruce
>
> ___
> Gnupg-users mailing list
> Gnupg-users@gnupg.org
> https://lists.gnupg.org/mailman/listinfo/gnupg-users
>
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


gpg: can't handle public key algorithm 18

2023-04-15 Thread Mike Schleif
On trying to decrypt a file, we get the subject error on failure.

What does this mean?

How ought we deal with this?

Please, advise. Thank you.

~ Mike
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users