"Ivo Gandolfo" wrote:
I've had the same problem as you in the past. Check your installed gpg
version, and that perl-nocem can read the right keyring. In my case the
keyring permissions file were wrong.
Thanks you Ivo for reply me and Bravo for your server management!
Before writing I checked the permission of keyring, is set 644 as perl-nocem helper, but I get the unknown error only on the key usenet ovh (EdDSA curve ed25519) others deletions work fine...
On my system are installed both versions of GPG, as follows:
"""
$ gpg --version
gpg (GnuPG) 1.4.23
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://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: ~/.gnupg
Algoritmi supportati:
A chiave pubblica: RSA, RSA-E, RSA-S, ELG-E, DSA
Cifrari: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compressione: Non compresso, ZIP, ZLIB, BZIP2
"""
"""
$ gpg2 --version
gpg (GnuPG) 2.4.4
libgcrypt 1.10.3
Copyright (C) 2024 g10 Code GmbH
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: /usr/inn/.gnupg
Algoritmi gestiti:
A chiave pubblica: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cifrari: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compressione: Non compresso, ZIP, ZLIB, BZIP2
"""
I checked and modified, specifically for call gpg2 and gpgv2 the file Config.pm, and
actually called gpg2 during the deletion, (I personally checked the accton log)
however the error remains.
I've had the same problem as you in the past. Check your installed gpg version, and that perl-nocem can read the right keyring. In my case the keyring permissions file were wrong.
F/U to the correct group news.software.nntpThanks you for suggestions and correction
If you originally imported the key with gpg1 you may need to re-import with gpg2.
I ran into that with this key on my system.42 :-(
ncmring.gpg
"Roberto CORRADO" wrote:
ncmring.gpg
sorry, and copy the file in /etc/inn/... and check permission a owner
all work fine.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 498 |
Nodes: | 16 (0 / 16) |
Uptime: | 73:42:56 |
Calls: | 9,819 |
Calls today: | 7 |
Files: | 13,757 |
Messages: | 6,189,859 |