On 03/10/2023 19:59, llp wrote:
Yes, it's a configuration problem on your server.
I checked that the GnuPG libraries are all installed, and they are, so
I assume it's a perl-nocem bug. Tomorrow I will write to Julien Elie
and ask for clarification.
and make sure it has the correct versions of gpg and gpgv:
our $gpgv = '/usr/bin/gpgv';
our $gpg = '/usr/bin/gpg2';
Seem's a problem of gpg, but I don't understand why.
Perhaps the difference in PubKey supported algorithms ?
On 04/10/2023 05:14, Ray Banana wrote:
and make sure it has the correct versions of gpg and gpgv:
our $gpgv = '/usr/bin/gpgv';
our $gpg = '/usr/bin/gpg2';
Just checked, /usr/bin/gpg2 it's a symlink point to /usr/bin/gpg.
root@paganini:~# /usr/bin/gpg --version
gpg (GnuPG) 2.2.27
libgcrypt 1.9.4
Copyright (C) 2021 Free Software Foundation, Inc.
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /root/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
Seem's a problem of gpg, but I don't understand why.
On 04/10/2023 09:25, llp wrote:
Seem's a problem of gpg, but I don't understand why.
Perhaps the difference in PubKey supported algorithms ?
And this is precisely the strange thing, given that the libgcrypt
library is the same.
This is a configure option in gpg:
--disable-gpg-rsa disable the RSA public key algorithm in gpg
--disable-gpg-ecdh disable the ECDH public key algorithm in gpg
--disable-gpg-ecdsa disable the ECDSA public key algorithm in gpg
--disable-gpg-eddsa disable the EdDSA public key algorithm in gpg
Your version of gpg seems to have been built with some of these options.
What is your operating system and distribution?
root@paganini:~# lsb_release -acd
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
gpg installed with apt, no change or customized packet.
root@paganini:~# /usr/bin/gpg --version
gpg (GnuPG) 2.2.27
libgcrypt 1.9.4
Copyright (C) 2021 Free Software Foundation, Inc.
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /root/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
On 04/10/2023 10:09, Ray Banana wrote:
This is a configure option in gpg:
--disable-gpg-rsa disable the RSA public key algorithm in gpg
--disable-gpg-ecdh disable the ECDH public key algorithm in gpg
--disable-gpg-ecdsa disable the ECDSA public key algorithm in gpg
--disable-gpg-eddsa disable the EdDSA public key algorithm in gpg
Your version of gpg seems to have been built with some of these options.
What is your operating system and distribution?
root@paganini:~# lsb_release -acd
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
gpg installed with apt, no change or customized packet.
Seems to be something specific to Ubuntu, or perhaps the age of the
package. Debian unstable supports it:
On 04/10/2023 17:49, Russ Allbery wrote:
Seems to be something specific to Ubuntu, or perhaps the age of the
package. Debian unstable supports it:
After several tests (and reinstallation of the package itself) I decided that a "clean" solution isn't enough, so I went with the "dirty" solution. I brutally grabbed the libgcrypt20 package from the lunar lobster 22.10 repository, and now the output is:
root@paganini:~# /usr/bin/gpg --version
gpg (GnuPG) 2.2.27
libgcrypt 1.10.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /root/.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
problem solved, have fun.
Sincerely
After several tests (and reinstallation of the package itself) I decided
that a "clean" solution isn't enough, so I went with the "dirty"
solution. I brutally grabbed the libgcrypt20 package from the lunar
lobster 22.10 repository, and now the output is:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 19:02:42 |
Calls: | 10,389 |
Files: | 14,061 |
Messages: | 6,416,958 |