GPG cannot import public key
Daniel Axtens
daniel at axtens.net
Sat Apr 26 03:06:34 CEST 2014
I can confirm that - I compiled GnuPG against the latest version of libgcrypt in git, and it imported the second key fine.
gpg2 --version
gpg (GnuPG) 2.0.22
libgcrypt 1.7.0-beta61
Daniel
On 25/04/2014, at 7:57 PM, Werner Koch <wk at gnupg.org> wrote:
> On Thu, 24 Apr 2014 19:55, dshaw at jabberwocky.com said:
>
>> I'm afraid I don't have immediate access to the GPG 2.x code base to check, but I wonder if your problem is simply that 2.x doesn't accept RSA_S and RSA_E keys?
>
> There is indeed a bug related to the use of RSA_S and RSA_E if GnuPG 2.0
> is used with Libgcrypt 1.6. It is fixed in the repos and I consider to
> do a new libgcrypt release soon (we can fix it at both places).
>
>
> Salam-Shalom,
>
> Werner
>
> --
> Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
>
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </pipermail/attachments/20140426/e4a3aaba/attachment.sig>
More information about the Gnupg-users
mailing list