Hi,
Werner Koch wrote:
> I looked at the Fedora Libgcrypt source and noticed that they ship
> libgcrypt with the nistp192 and all brainpool curves removed. I have
> not yet build this version but given that one of your keys has brainpool
> curves this might be the culprit.
>
> I can understand
On Mon, 30 Nov 2020 22:20, Werner Koch said:
> I'll build with the Fedora patches in the next days. If the missing
> curves are really the reason, we can fix that.
Yes, the disabled Brainpool curves lead to the import problem. I'll see
what we can do. See https://dev.gnupg.org/T5162
Hi!
I looked at the Fedora Libgcrypt source and noticed that they ship
libgcrypt with the nistp192 and all brainpool curves removed. I have
not yet build this version but given that one of your keys has brainpool
curves this might be the culprit.
I can understand that they remove nistp192 for
On Mon, 30 Nov 2020 09:25, Robert J. Hansen said:
> I'll send the keyring onto you privately.
Thanks. Unfortunately i was not able to replicate the bug on my Devuan
box. I tried using the same Libgcrypt version but with some libraries
different. Should not matter, though.
> * Libgcrypt 1.8.7
The first one is the real error. We can't compute the keygrip for the
public key. If you can build gpg yourself please apply this patch:
It's a standard Fedora GnuPG, so although I'm sure a source RPM is
available I'm not enough of an RPM surgeon to know how to modify the
.rpmspec to apply
Hi!
On Mon, 30 Nov 2020 04:16, Robert J. Hansen said:
> gpg: kbx: error computing keygrip
> gpg: error writing keyring '/home/rjh/.gnupg/pubring.kbx': General error
The first one is the real error. We can't compute the keygrip for the
public key. If you can build gpg yourself please apply
This should not be happening, but is. From a completely clean
installation, importation of legitimate OpenPGP keys results in strange
general failures. The system is an x64 Fedora 33 box running GnuPG
2.2.24 on libgcrypt 1.8.6.
I'm happy to provide the keys.asc file to any GnuPG dev who
