mpi too large

David Shaw dshaw at
Fri Dec 16 14:32:11 CET 2005

On Thu, Dec 08, 2005 at 02:11:27PM -0500, Bigda, Faith wrote:
> I've been researching and I can't seem to determine what the problem is with the key.  It appears to have a bad signature?  I imported the key and do an edit check:
> C:\GnuPG>gpg --import xx.asc
> gpg: key F867286A: public key "Named File Transfer" imported
> gpg: Total number processed: 1
> gpg:               imported: 1
> C:\GnuPG>gpg --edit-key F867286A
> gpg (GnuPG) 1.2.3; Copyright (C) 2003 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.
> gpg: checking the trustdb
> gpg: checking at depth 0 signed=0 ot(-/q/n/m/f/u)=0/0/0/0/0/7
> This key may be revoked by DSA key 8C5F4D13 [?]
> pub  1024D/F867286A  created: 2004-11-09 expires: never      trust: -/-
> sub  3072g/EC820541  created: 2004-11-09 expires: never
> (1). Named File Transfer
> Command> check
> uid  Named File Transfer
> sig!        F867286A 2004-11-09   [self-signature]
> 1 signature not checked due to a missing key
> Command>
> The problem is that even if I follow through and TRUST it anyway,
> when I try to decrypt a file from them I get an error: "mpi too
> large".  I don't know if the problems are even related.

Probably unrelated.  The "signature not checked" is not an error, but
normal operation: the key you imported has a signature from a key you
don't have.  It's just a note so you can go out and get this other key
if you care.

The "mpi too large" is a problem, but likely on the sender side.  Do
you know what program they are using to encrypt?


More information about the Gnupg-users mailing list