mailcrypt/PGG woes

mailcrypt/PGG woes

[Matthias Andree]

Hi,

I'm using Gnus from CVS (freshly pulled, built and installed) with GNU
emacs 21.3.1. I have some issues with traditional GPG signatures in some
groups, say, gmane.network.leafnode.announce on news.gmane.org (NNTP
access). The articles are traditional gpg --clearsign format.

When I choose any article of mine and type C-c / v (Mailcrypt
verify), I'm getting "bad signature, doesn't match file contents."

pgg-verify brabbles something about NODATA and seems not to find the
signature, but marking just the signed part and then doing
"pgg-verify-region" tells me the signature is intact.

What's up here?

-- 
Matthias Andree

Re: mailcrypt/PGG woes

[Matthias Andree]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> pgg-verify brabbles something about NODATA and seems not to find the
> signature, but marking just the signed part and then doing
> "pgg-verify-region" tells me the signature is intact.

Gna, one of the bogus error messages in Gnus caused the dupe. Why do
Netscape 4 bugs get introduced into Gnus? :->

<ducks & runs for cover>

-- 
Matthias Andree

Re: mailcrypt/PGG woes

[Simon Josefsson]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> No error message?  Could you forward a copy of the mail?  (Or a
>> similar behaving one without sensitive information.)
>
> such mail is available from the public NNTP server news.gmane.org in
> gmane.network.leafnode.announce.

They verify fine here with Emacs 20 after pressing W s.

> Note the failing mail is "traditional pgp" as mutt calls it, not MIME. A
> PGP/MIME signed multipart that Oliver Braun sent to one of the FreeBSD
> mailing lists recently displayed fine, pressing `W s' on that mail then
> verifies the signature and adds a bold button to the top with the
> results.
>
> I'm attaching a mail that shows this problem. I hope attaching it
> doesn't make the problem disappear.

The attached copy was filled, so the signature didn't work.  But
pressing `W s' on your message tried to verify it, and displayed the
MIME buttons (just like the original messages).

Re: mailcrypt/PGG woes

[Matthias Andree]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> No error message?  Could you forward a copy of the mail?  (Or a
>> similar behaving one without sensitive information.)
>
> such mail is available from the public NNTP server news.gmane.org in
> gmane.network.leafnode.announce.
>
> Note the failing mail is "traditional pgp" as mutt calls it, not MIME. A
> PGP/MIME signed multipart that Oliver Braun sent to one of the FreeBSD
> mailing lists recently displayed fine, pressing `W s' on that mail then
> verifies the signature and adds a bold button to the top with the
> results.

Strangely enough, (require 'mml1991) defines the mml1991-use variable to
pgg, but this doesn't fix the verification issue, `W s' still doesn't
seem to work. I'm at a loss.

-- 
Matthias Andree

Re: mailcrypt/PGG woes

[Matthias Andree]

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

Simon Josefsson <jas@extundo.com> writes:

> No error message?  Could you forward a copy of the mail?  (Or a
> similar behaving one without sensitive information.)

such mail is available from the public NNTP server news.gmane.org in
gmane.network.leafnode.announce.

Note the failing mail is "traditional pgp" as mutt calls it, not MIME. A
PGP/MIME signed multipart that Oliver Braun sent to one of the FreeBSD
mailing lists recently displayed fine, pressing `W s' on that mail then
verifies the signature and adds a bold button to the top with the
results.

I'm attaching a mail that shows this problem. I hope attaching it
doesn't make the problem disappear.

-- 
Matthias Andree

[-- Attachment #2: xb --]
[-- Type: message/rfc822, Size: 4507 bytes --]

From: Matthias Andree <matthias.andree@gmx.de>
To: leafnode-announce@lists.sourceforge.net
Subject: Leafnode 1.9.38.rel released (STABLE)
Date: Wed, 23 Apr 2003 18:37:49 +0200
Message-ID: <20030423163749.GB19138@merlin.emma.line.org>

-----BEGIN PGP SIGNED MESSAGE-----

                ----------------------------------------
                 leafnode 1.9.38.rel has been released.
                ----------------------------------------

Leafnode 1.9.38 has been released and replaces the withdrawn 1.9.37
version of leafnode. Leafnode 1.9.37 tried to fix the replacement
snprintf that is used on systems with inadequate native snprintf() that
had been broken for a long time, but the fixes in 1.9.37 were not
complete; leafnode 1.9.37 was reported broken among other systems from
FreeBSD 4.8. Please apologize the inconvenience.

Leafnode 1.9.38 also improves NewsCache compatibility and has tighter
checks to make sure that the prerequisites are there when building the
RPM binary package.

Note that you can subscribe to a moderated (non-spam) leafnode-announce
mailing list or you can watch file releases at sourceforge below, if you
want to be notified when new leafnode releases become available.

Leafnode 1.9.38 is or will become available in .tar.bz2 format from these sites:

o SourceForge -- this site also carries patches to make 1.9.36/37 into 1.9.38
   http://sourceforge.net/projects/leafnode/
   http://sourceforge.net/project/showfiles.php?group_id=57767&release_id=154765
   rsync://osdn.dl.sourceforge.net/sourceforge/leafnode/

   Patch:
   http://sourceforge.net/project/showfiles.php?group_id=57767&release_id=154764

o Dortmund University -- this site also carries .tar.gz tarballs
    http://mandree.home.pages.de/leafnode/
    rsync://www.dt.e-technik.uni-dortmund.de/leafnode-1/

o IBiblio/MetaLab (will take some days to pick up) -- has FTP sites
    http://ibiblio.org/pub/Linux/MIRRORS.html
    Check the system/news/transport directory

o Würzburg University
    http://www.leafnode.org/


NOTE that the .gz tarballs are EXCLUSIVELY
available from http://mandree.home.pages.de/leafnode/, and the upgrade
patches are only available from sourceforge and
http://mandree.home.pages.de/leafnode/. They are not on ibiblio or
http://www.leafnode.org/

SHA1 checksums:
0b9df2db6cc3e2f296ac389c06a96caaafde2868 *leafnode-1.9.38.rel.tar.bz2
7401dcc7af52fc361387f09ec11456e8f8f90269 *leafnode-1.9.38.rel.tar.gz

MD5 checksums:
684d47a127393d7c6755b371b7d70046 *leafnode-1.9.38.rel.tar.bz2
6760cba38e1f9d9c6516fef8e0239d99 *leafnode-1.9.38.rel.tar.gz

File sizes: (K = 1024 Bytes)
608K leafnode-1.9.38.rel.tar.bz2
760K leafnode-1.9.38.rel.tar.gz

The .bz2 format is used by the OpenSource bzip2 compressor that is
available from http://sources.redhat.com/bzip2/

Below is the NEWS file excerpt, with changes since leafnode-1.9.37. The
full ChangeLog ships with the tarballs and can be viewed at
http://mandree.home.pages.de/leafnode/ChangeLog.txt

Have fun,
Matthias Andree, Leafnode maintainer

,-----------------------------------------------------------------------------
* 1.9.38, 2003-04-23

### BUGFIX
o The replacement snprintf trampled hash marks over digits in the output when
  the output length matched the minimum field width or exceeded it, in
  violation of Single Unix Specification. Fixed now. (Corresponding
  conformance testing code has been added to "make check".)

### CHANGES
o The RPM spec file checks if pcre.h is in /usr/include/pcre or /usr/include.
  This hopefully addresses RedHat 9 RPM build failures. (The leafnode RPM
  should rely on the pcre RPM rather than including its own copy of PCRE
  files, to avoid conflicts.) This is untested because the snprintf bugfix
  above is critical and does not allow for further delay for testing.
o The NewsCache compatibility code was changed to allow the DATE command
  for NewsCache 0.99.22* and 0.99.2? as well as 1.1.12 and newer.
`-----------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iQCVAwUBPqbBVSdEoB0mv1ypAQFJVgP/WSOoSMi2dcZ/lWgFTXaviN6718l2Z/5o
qhjRPIWOMWyCV68C0n1ABH8HBH5TwZ0gjjSGUAkuQJOPtcJagYw+vhbQ85Uhv118
UEDIH8B4lfo+bxjUp+L6CvgJXyGtP5qBYo2tsPaUKOnhIYhcDO9Od5aDOzEFaUAT
lAoCahM1q9o=
=I3/Z
-----END PGP SIGNATURE-----

Re: mailcrypt/PGG woes

[Matthias Andree]

On Fri, 25 Apr 2003, Simon Josefsson wrote:

> mml1991-use isn't customizable, but C-h v mml1991-use RET will tell
> what value it has.  It should be pgg.

I don't have such a variable. C-h v doesn't offer mml1991 for
completion if I try this in the summary buffer.

I do have mml2015-use, which is pgg and which is defined in mml2015.

The corresponding file is mml2015.el by Shenghuo Zhu, it's the one
installed by Gnus.

-- 
Matthias Andree

Re: mailcrypt/PGG woes

[Simon Josefsson]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

>>> pgg-verify brabbles something about NODATA and seems not to find the
>>> signature, but marking just the signed part and then doing
>>> "pgg-verify-region" tells me the signature is intact.
>>
>> How did you invoke pgg-verify?
>
> M-x pgg-verify RET

In which buffer?  PGG is not Gnus aware, so you must invoke it in a
proper buffer with the real OpenPGP message shown, doing it from the
summary buffer won't work.

>> The recommended way is to invoke it via Gnus with, e.g., `W s'.  What
>> happens if you do this? (Make sure you haven't changed mml1991-use
>> from its default value.)
>
> W s is apparently not doing anything on my machine (just updated Gnus
> from CVS again), it just jumps to the top of the message. I don't have a
> mml1991-use variable to customize either.

No error message?  Could you forward a copy of the mail?  (Or a
similar behaving one without sensitive information.)

mml1991-use isn't customizable, but C-h v mml1991-use RET will tell
what value it has.  It should be pgg.

Re: mailcrypt/PGG woes

[Matthias Andree]

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> On Wed, Apr 23 2003, Matthias Andree wrote:
>
>> When I choose any article of mine and type C-c / v (Mailcrypt
>> verify), I'm getting "bad signature, doesn't match file contents."
>
> Why do you still use Mailcrypt?

I killed it now, still no difference.

> I have set `gnus-buttonized-mime-types' to '(".*/signed").  When I hit
> RET on the button in
> <URL:nntp://news.gmane.org/gmane.network.leafnode.announce/15>, it
> verifies correctly.  A second RET gives:

I don't have a button, I see the raw message after decoding q-p. "W s"
does nothing apparently. If I press "K m"
(gnus-summary-repair-multipart), it prints it's not saving the article
because the group is read-only (I'm reading nntp from news.gname.org),
and I see the full header, the GPG boundaries removed and the article
with _undecoded_ quoted-printable (with trailing = and =3D and all that).

> Ah, `W s' (or <menu-bar> <Article> <MIME> <Verify and Decrypt>)
> probably...
>
> ,----[ `C-h k W s' ]
> | W s runs the command gnus-summary-force-verify-and-decrypt
> |    which is an interactive compiled Lisp function in `gnus-sum'.
> | (gnus-summary-force-verify-and-decrypt)
> | 
> | Display buttons for signed/encrypted parts and verify/decrypt them.
> `----

C-h k W s does print the same, but it's non-functional here, see my
other mail.

-- 
Matthias Andree

Re: mailcrypt/PGG woes

[Matthias Andree]

Simon Josefsson <jas@extundo.com> writes:

> Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
>
>> Hi,
>>
>> I'm using Gnus from CVS (freshly pulled, built and installed) with GNU
>> emacs 21.3.1. I have some issues with traditional GPG signatures in some
>> groups, say, gmane.network.leafnode.announce on news.gmane.org (NNTP
>> access). The articles are traditional gpg --clearsign format.
>>
>> When I choose any article of mine and type C-c / v (Mailcrypt
>> verify), I'm getting "bad signature, doesn't match file contents."
>
> This sounds like a mailcrypt problem, not PGG.
>
>> pgg-verify brabbles something about NODATA and seems not to find the
>> signature, but marking just the signed part and then doing
>> "pgg-verify-region" tells me the signature is intact.
>
> How did you invoke pgg-verify?

M-x pgg-verify RET

> The recommended way is to invoke it via Gnus with, e.g., `W s'.  What
> happens if you do this? (Make sure you haven't changed mml1991-use
> from its default value.)

W s is apparently not doing anything on my machine (just updated Gnus
from CVS again), it just jumps to the top of the message. I don't have a
mml1991-use variable to customize either.

-- 
Matthias Andree

Re: mailcrypt/PGG woes

[Simon Josefsson]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> Hi,
>
> I'm using Gnus from CVS (freshly pulled, built and installed) with GNU
> emacs 21.3.1. I have some issues with traditional GPG signatures in some
> groups, say, gmane.network.leafnode.announce on news.gmane.org (NNTP
> access). The articles are traditional gpg --clearsign format.
>
> When I choose any article of mine and type C-c / v (Mailcrypt
> verify), I'm getting "bad signature, doesn't match file contents."

This sounds like a mailcrypt problem, not PGG.

> pgg-verify brabbles something about NODATA and seems not to find the
> signature, but marking just the signed part and then doing
> "pgg-verify-region" tells me the signature is intact.

How did you invoke pgg-verify?  The recommended way is to invoke it
via Gnus with, e.g., `W s'.  What happens if you do this? (Make sure
you haven't changed mml1991-use from its default value.)

Re: mailcrypt/PGG woes

[Reiner Steib]

On Wed, Apr 23 2003, Matthias Andree wrote:

> When I choose any article of mine and type C-c / v (Mailcrypt
> verify), I'm getting "bad signature, doesn't match file contents."

Why do you still use Mailcrypt?

I have set `gnus-buttonized-mime-types' to '(".*/signed").  When I hit
RET on the button in
<URL:nntp://news.gmane.org/gmane.network.leafnode.announce/15>, it
verifies correctly.  A second RET gives:

,----
| [[PGP Signed Part:Matthias Andree <matthias.andree@gmx.de>
| Untrusted, Fingerprint: 7214 8B1D 6718 3E5B 03B7 D7D8 0F1E F455]
| Warning: using insecure memory!
| Signature made Wed Apr 23 18:37:41 2003 CEST using RSA key ID 26BF5CA9
| Good signature from "Matthias Andree <matthias.andree@gmx.de>"
| [...]
`----

> pgg-verify brabbles something about NODATA and seems not to find the
> signature, but marking just the signed part and then doing
> "pgg-verify-region" tells me the signature is intact.

Hm, how are users who don't have ".*/signed" in
`gnus-buttonized-mime-types' supposed to verify the signature?
Do `K m' first?

Ah, `W s' (or <menu-bar> <Article> <MIME> <Verify and Decrypt>)
probably...

,----[ `C-h k W s' ]
| W s runs the command gnus-summary-force-verify-and-decrypt
|    which is an interactive compiled Lisp function in `gnus-sum'.
| (gnus-summary-force-verify-and-decrypt)
| 
| Display buttons for signed/encrypted parts and verify/decrypt them.
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

mailcrypt/PGG woes

[Matthias Andree]

Hi,

I'm using Gnus from CVS (freshly pulled, built and installed) with GNU
emacs 21.3.1. I have some issues with traditional GPG signatures in some
groups, say, gmane.network.leafnode.announce on news.gmane.org (NNTP
access). The articles are traditional gpg --clearsign format.

When I choose any article of mine and type C-c / v (Mailcrypt
verify), I'm getting "bad signature, doesn't match file contents."

pgg-verify brabbles something about NODATA and seems not to find the
signature, but marking just the signed part and then doing
"pgg-verify-region" tells me the signature is intact.

What's up here?

-- 
Matthias Andree