Your message dated Thu, 16 Jul 2009 13:59:34 +0200
with message-id <1247745574.5922.45.ca...@leidi>
and subject line Bug#151656: gnupg: Ohhhh jeeee: mpi crosses packet
bordersecmem usage...
has caused the Debian Bug report #151656,
regarding Ohhhh jeeee: mpi crosses packet bordersecmem usage...
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
151656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=151656
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.0.7
Severity: normal
When fetching the key 767EFC24 from pgp.dtype.org the following happens:
wea...@odyssey:~$ gpg --keyserver pgp.dtype.org --recv 767EFC24
gpg: requesting key 767EFC24 from pgp.dtype.org ...
gpg: invalid radix64 character 2e skipped
gpg: invalid radix64 character 3a skipped
gpg: invalid radix64 character 5f skipped
gpg: invalid radix64 character 2e skipped
gpg: invalid radix64 character 2e skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 3a skipped
gpg: invalid radix64 character 3c skipped
gpg: invalid radix64 character 3e skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 60 skipped
gpg: invalid radix64 character 60 skipped
gpg: invalid radix64 character 27 skipped
gpg: invalid radix64 character 27 skipped
gpg: invalid radix64 character 3c skipped
gpg: invalid radix64 character 3e skipped
gpg: invalid radix64 character 3c skipped
gpg: invalid radix64 character 3e skipped
gpg: invalid radix64 character 3c skipped
gpg: invalid radix64 character 3e skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 60 skipped
gpg: invalid radix64 character 60 skipped
gpg: invalid radix64 character 27 skipped
gpg: invalid radix64 character 27 skipped
gpg: invalid radix64 character 3c skipped
gpg: invalid radix64 character 3e skipped
gpg: invalid radix64 character 3c skipped
gpg: invalid radix64 character 3e skipped
gpg: invalid radix64 character 3c skipped
gpg: invalid radix64 character 3e skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 2d skipped
gpg: invalid radix64 character 3a skipped
gpg: invalid radix64 character 2e skipped
gpg: invalid radix64 character 3a skipped
gpg: invalid radix64 character 2e skipped
gpg: invalid radix64 character 2e skipped
gpg: Ohhhh jeeee: mpi crosses packet bordersecmem usage: 0/0 bytes in 0/0
blocks of pool 0/16384
Aborted
It works without any problems from pgp.mit.edu so the key on dtype.org
is probably corrupt. Even then gnupg should not fail like that.
yours,
peter
--
PGP signed and encrypted | .''`. ** Debian GNU/Linux **
messages preferred. | : :' : The universal
| `. `' Operating System
http://www.palfrader.org/ | `- http://www.debian.org/
pgpVtMQcWUYSt.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,
I'm going to close this report and #237253 because they are missing the
requested information. So no proof is available, that the problem still
exists in gnupg 1.4.x. Please feel free to comment my decision and/or
reopen your report if necessary.
Regards, Daniel
--- End Message ---
