Am Montag 16 April 2007 schrieb Werner Koch:
> Hi,
>
> I think I found the problem: In g10/gpg.h you find
>
> /* Number of bits we accept when reading or writing MPIs. */
> #define MAX_EXTERN_MPI_BITS 16384
>
> when writing it out with build-packet.c:mpi_write, we use a buffer if
> that length
Am Montag 16 April 2007 schrieb Charly Avital:
> Werner Koch wrote the following on 4/16/07 2:48 PM:
> [...]
>
> > GPG 2.x uses libgcrypt for crypto operations and this includes keyid
> > calculations and converting of big integers. It really would make sense
> > to check again using the latest st
g
2.0.x this would explain the behaviour. The key gets written out incorrectly
and gnupg 1.4.7 fails because of this.
Is there any easy way to view and compare the key material (prime product,
public exponent...) of a key ring?
Alexander Feigl
___
Gnup
Charly Avital wrote::
> Alexander Feigl wrote the following on 4/7/07 9:30 PM:
> [...]
>
> > I pasted a testing key below. The key with the key id 0x2D879666 gets
> > imported as 0xB61454A3 here.
> >
> > While such large keys seem like overkill. But gnupg also s
e key id 0x2D879666 gets imported
as 0xB61454A3 here.
While such large keys seem like overkill. But gnupg also supports the SHA512
hash which would require such large keys for sensible use.
Alexander Feigl
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.3 (G
