Miscalculated Key ID and fingerprints when compiled for ARM

[David Shaw]

On Feb 1, 2010, at 11:05 PM, Rich Jones wrote:

> Hello!
> 
> I have complied a version of GPG for an ARM-based processor (this is
> actually running a T-Mobile G1). I have found an interesting and
> unfortunately fatal bug.
> 
> All imported keys are invalid as there is a miscalculated key ID and
> fingerprint.
> 
> For example, on my real machine, --list-keys gives:
> 
> pub   1024D/A1D39D09 2008-04-23
> uid                  John M. Schanck <jms07 at hampshire.edu>
> uid                  John M. Schanck <john at anomos.info>
> sub   2048g/2B4C51FB 2008-04-23
> 
> but on the ARM version, the same command on the same imported key gives:
> 
> pub   1024D/5267F8D8 2008-04-23
> uid                  John M. Schanck <jms07 at hampshire.edu>
> uid                  John M. Schanck <john at anomos.info>
> 
> The binary was compiled with the command: ./configure CC=gnupg-agcc
> --host=arm-eabi --prefix=/data/data/org.gnupg.android.gnupg/
> --disable-idea --disable-finger --disable-largefile
> --with-zlib=$DROID/src/external/zlib
> --with-bzip2=$DROID/external/bzip2 --with-included-regex
> --disable-photo-viewers

Hmm.  A few things to try:

What sort of machine is your "real machine"?

Try adding --disable-endian-check to your configure line.

Also, what happens if you do:

  echo test | gpg --print-md sha1

On both your real machine and on the ARM machine?

David