Gnupg cannot handle extremely large keys on 32 bit Linux

[Charly Avital]

Ludwig Hügelschäfer wrote the following on 4/14/07 4:45 PM:
> Hi,
> 
> Charly Avital wrote on 14.04.2007 15:18 Uhr:
> 
>> I can't qualify whether it works or not, nor can I qualify whether the
>> key ID is incorrect.
> 
>> GnuPG recognizes 17CACAE3 (in both processors) as the key ID.
> 
> Perhaps I may help here:
> 
> Using gnupg 1.4.7, self compiled with idea-support under Mac OS X
> 10.4.9, PPC (have no intel around yet) I get these results after cutting
> and pasting the key from the OP and saving with Textwrangler:
> 
> 
> gpg --import test.asc
> gpg: key 2D879666: public key "Testing only <test at test.test>" imported
> gpg: Total number processed: 1
> gpg:               imported: 1  (RSA: 1)
> 
> gpg --list-keys
> /Users/<justme>/.gnupg/pubring.gpg
> pub   16384R/2D879666 2007-04-07 [expires: 2017-04-04]
> uid                  Testing only <test at test.test>
> 
> gpg --edit-key 0x2D879666
> gpg (GnuPG) 1.4.7; Copyright (C) 2006 Free Software Foundation, Inc.
> This program comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions. See the file COPYING for details.
> 
> 
> pub  16384R/2D879666  created: 2007-04-07  expires: 2017-04-04  usage: SC
>                      trust: unknown       validity: unknown
> [ unknown] (1). Testing only <test at test.test>
> 
> Command> fpr
> pub   16384R/2D879666 2007-04-07 Testing only <test at test.test>
>  Primary key fingerprint: BCA2 2448 8F7C 5646 A94A  CE16 35BE A302 2D87 9666
> 
> Command> check
> uid  Testing only <test at test.test>
> sig!3        2D879666 2007-04-07  [self-signature]
> 
> Command> showpref
> [ unknown] (1). Testing only <test at test.test>
>      Cipher: AES256, AES192, AES, CAST5, 3DES
>      Digest: SHA512, SHA384, SHA256, SHA1, RIPEMD160
>      Compression: BZIP2, ZLIB, ZIP, Uncompressed
>      Features: MDC, Keyserver no-modify
> 
> Seems correct after reading all posts.
> 
> HTH
> 
> Ludwig

David,

After reading Ludwig's post, I proceeded to import Feigl's key, using
the same procedure he followed.

You might remember that when I originally imported Feigl's key, I used
Thunderbird+Enigmail's OpenPGP option to import the key block (I
remember I expressly reported it), without having to copy+paste+save in
a stand alone file.

Now, when I import the stand alone file I created, I get the following
in Terminal:
----------------
$ gpg --import /Users/admin/Desktop/Feigl.unix
gpg: key 2D879666: public key "Testing only <test at test.test>" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
admin-s-computer:~ admin$ gpg --edit-key 2D879666
gpg (GnuPG) 1.4.7; Copyright (C) 2006 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.


pub  16384R/2D879666  created: 2007-04-07  expires: 2017-04-04  usage: SC
                     trust: unknown       validity: unknown
[ unknown] (1). Testing only <test at test.test>

Command> check
uid  Testing only <test at test.test>
sig!3        2D879666 2007-04-07  [self-signature]

Command> fpr
pub   16384R/2D879666 2007-04-07 Testing only <test at test.test>
 Primary key fingerprint: BCA2 2448 8F7C 5646 A94A  CE16 35BE A302 2D87 9666

Command> quit
----------------------

*Therefore, there is a difference in results (Key ID and fpr) when the
keyblock is imported from Thunderbird+Enigmail (inside option), and when
the same keyblock is saved in a stand-along file that is imported via CLI*.

By the way, I also reported that PGP Desktop (where the importing is
done by drag/dropping the stand-alone file into PGP's open window)
recognized the key as 0x2D879666 (with an invalid self-signature).

I don't know why there is a difference, I am including Patrick
Brunschwig (Enigmail) in the distribution of this message.

Charly