Keys which leave GnuPG unusable
Weimer at CERT.Uni-Stuttgart.DE
Fri Jun 7 22:23:02 CEST 2002
"Robert J. Hansen" <rjhansen at inav.net> writes:
> With GnuPG 1.0.6, it'll throw a fit about an MPI being too large and will
> segfault. You can import it just fine, but once you import it, all
> further operations crash and burn.
It's probably an encrypted MPI started with a zero octet. This
problem is already known, I think.
Workaround: Create a new directory, copy the secret key (in
non-armored from) to "secring.gpg", use "gpg --home . --edit-key" to
change the passphrase. It's likely that the result is readable by
GnuPG (the bug is triggered with a probability of 1:85 or so).
Florian Weimer Weimer at CERT.Uni-Stuttgart.DE
University of Stuttgart http://CERT.Uni-Stuttgart.DE/people/fw/
RUS-CERT +49-711-685-5973/fax +49-711-685-5898
More information about the Gnupg-devel