[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mutt-users
Subject:    GnuPG, first lines lost after verifying sig?
From:       Chris De Young <chd () chud ! net>
Date:       2005-01-28 23:48:46
Message-ID: 20050128234846.GA9384 () dionysus ! chud ! net
[Download RAW message or body]

Hello,

I've run across an odd behavior with Mutt and GnuPG.  In a few cases,
after mutt verifies the signature on a message with an inline (not
MIME) signature, it chops off the first couple of lines when
displaying the message.

Thunderbird w/ Enigmail does not do this, which leads me to think that
it is not a GPG problem.

Here's an example, with Mutt 1.4.1i and GnuPG 1.4.0.

The original message, as I look at it the first time (+++ separator is
not part of the message):

+++++++++++++++++++++++++++++++++++++++++++++++

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Btw, the login info is as follows (for the director)

https://128.196.xxx.xxx:xxx/

login: admin
pwd: ...

[...]

+++++++++++++++++++++++++++++++++++++++++++++++

I've blacked out part of the IP address above, but it's simply digits
in the original message.

Now, I use 'check-traditional-pgp' to verify the signature, after
which what Mutt shows me is:

+++++++++++++++++++++++++++++++++++++++++++++++

[-- PGP output follows (current time: Fri 28 Jan 2005 04:27:30 PM MST) --]
gpg: Signature made Thu 27 Jan 2005 06:04:22 PM MST using DSA key ID 129B47CB
gpg: Good signature from "Rusma Mulyadi <rmulyadi@ms.telcom.arizona.edu>"
gpg: WARNING: Using untrusted key!

[-- End of PGP output --]

[-- BEGIN PGP SIGNED MESSAGE --]

https://128.196.xxx.xxx:xxx/

login: admin
pwd: ...

[...]

+++++++++++++++++++++++++++++++++++++++++++++++

Note that the first couple lines from the original message are now
gone.  I even looked at the copy of the message in /var/spool/mail
with a hex editor to make sure there aren't any funky non-printing
characters in the beginning of the message, but 0x0a (line feed) is
the only one.

It must be something in the message because I don't see this behavior
in messages from other senders, as far as I can tell, but... what's
going on here? :-)

Thanks!
-Chris
chd@arizona.edu


[prev in list] [next in list] [prev in thread] [next in thread]