- User Since
- Mar 27 2017, 4:48 PM (234 w, 4 d)
Feb 23 2021
Fixed in libgcrypt 1.9.2. Thanks!
Feb 5 2021
Looks like this has been addressed in af23ab5c5482d625ff52e60606cf044e2b0106c8. A quick test building the current version in master with --disable-asm worked for me.
Jan 29 2021
Building without "--disable-asm" works without any issues.
This should already be fixed in libgcrypt 1.9.1 by rCc6425a5537294dfe2beaafc9105f7af4ceac677f.
This is likely the same as https://dev.gnupg.org/T5277. Do you configure with --disable-asm? If so: it should work without.
Feb 24 2015
This issue seems to be gone with gnupg 2.1.2. Thanks for the fix :)
Dec 23 2014
Reducing priority from critical to urgent since there is now a workaround known:
- move .gnupg to .gnupg.old
- gpg --import .gnupg.old/pubring.gpg
- gpg --import .gnupg.old/secring.gpg
- cp .gnupg.old/trustdb.gpg .gnupg
I can send you both versions of the keyring, a defect and a working one.
Dec 22 2014
I can send my keyring to you but I would not like to make it public. Is a private
mail with a download link ok?