Mailing List Archive

incorrect chars
I've some problems with previous messages from Juergen A. Erhard, but
I'm unable to discover if this is a gpg, mutt, xemacs or what else
problem..
here comes the output from mutt/gpg:

---------------------------------------------------------------------------
Reply-To: g10@net.lut.ac.uk
Date: Sat, 2 Jan 1999 22:17:08 +0100 (CET)
X-Mailer: GNU Emacs 20.2.1 (i486-pc-linux-gnu)
Subject: [OT] MIME & Emacs

[.-- PGP output follows (current time: Tue Jan 5 13:01:29 1999) --]
gpg: Warning: using insecure memory!
gpg: NOTE: this is a development version!
gpg: invalid radix64 character fe 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: no valid OpenPGP data found.
gpg: block_filter 0x812a278: read error (size=8183,a->size=53508)
gpg: packet(14) with unknown version 12
gpg: Signature made Sat Jan 2 22:17:08 1999 CET using DSA key ID E1501E9F
gpg: Can't check signature: public key not found
gpg: block_filter: pending bytes!

[-- End of PGP output --]

[-- BEGIN PGP SIGNED MESSAGE --]

I'd like to do correct MIME signing... but the package I use (SEMI,
.....

and
-------------------------------------------------------------------------
From: "Juergen A. Erhard" <jae@ilk.de>
To: GPG Discussion <g10@net.lut.ac.uk>
Reply-To: g10@net.lut.ac.uk
Date: Sat, 2 Jan 1999 22:14:02 +0100 (CET)
X-Mailer: GNU Emacs 20.2.1 (i486-pc-linux-gnu)
Subject: Reorder userids?

[.-- PGP output follows (current time: Tue Jan 5 13:02:58 1999) --]
gpg: Warning: using insecure memory!
gpg: NOTE: this is a development version!
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: [don't know]: invalid packet (ctb=62) near 821
gpg: Signature made Sat Jan 2 22:14:02 1999 CET using DSA key ID E1501E9F
gpg: Can't check signature: public key not found
gpg: no valid OpenPGP data found.

[-- End of PGP output --]

[-- BEGIN PGP SIGNED MESSAGE --]

I looked, but did not find a way to reorder user ids... okay, you can
...

-------------------------

Any hint?


--
Fabio Coatti http://felix.unife.it/~cova
Ferrara Linux Users Group http://flug.unife.it
GnuPG fp:6AB9 277E 9AA7 9D20 E82C 9EE7 2D17 E351 3DCB 0CDC
Old SysOps never die... they simply forget their password.
Re: incorrect chars [ In reply to ]
Fabio Coatti <cova@felix.unife.it> writes:

> gpg: invalid radix64 character fe skipped

I'm currently rewriting the armor stuff - I hope to solve all these
problems with the new and maintainable code.


Werner
Re: incorrect chars [ In reply to ]
On Tue, Jan 05, 1999 at 01:10:34PM +0100, Fabio Coatti wrote:
> I've some problems with previous messages from Juergen A. Erhard, but
> I'm unable to discover if this is a gpg, mutt, xemacs or what else
> problem..

It's an xemacs problem: The data were tagged as quoted-printable,
but the PGP armor was not encoded. This led to funny effects
wherever an equal sign occured in the armor, thus corrupting the
armor.

(Will this bug ever vanish from earth? Pegasus Mail for Windows did
the same thing.)

tlr
--
Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/
2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1
> Hi! I'm Signature Virus 99! Copy me into your signature and join the fun!
Re: incorrect chars [ In reply to ]
On Tue, Jan 05, 1999 at 03:23:12PM +0100, Werner Koch wrote:

> I'm currently rewriting the armor stuff - I hope to solve all these
> problems with the new and maintainable code.

You won't be able to solve this problem. The armor _is_ corrupt.


tlr
--
Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/
2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1
> Hi! I'm Signature Virus 99! Copy me into your signature and join the fun!