Recent changes to bugs

Perl 5.8

Frank Tobin — Thu, 03 Apr 2003 09:15:33 -0000

Perl 5.8.0
gpg (GnuPG) 1.2.1
pgpenvelope 2.10.2

Upon processing messages in either Pine or procmail,
pgpenvelope_decrypt fails to verify messages. GnuPG
reports getting no input. Everything works dandy from
the command line.

Attached is an rfc822 message which is signed.

blocking in Pine with quintuple-agent

Frank Tobin — Fri, 12 Apr 2002 17:03:12 -0000

Cristian Ionescu-Idbohrn has reported a problem that
when using the following setup:

pgpenvelope 2.10.2
quintuple-agent
Pine 4.44
Perl 5.6.1
Debuan/GNU Linux

that the attached file will cause pgpenvelope_decrypt
to block.

The situation does appear to happen outside of Pine.
I have not been able to duplicate this behaviour with
my differences beeing FreeBSD 4.5, Perl 5.005.

mail headers within body confuse pgpenve

Tue, 11 Dec 2001 17:22:21 -0000

there is a problem filtering mail replys from user that do not use pgp or similar and include the original singature + mail header when replying. pgpenvelope mixes up the headers + bodies found inside mail body. the following message is received:

Date: Tue, 11 Dec 2001 18:09:58 +0100 (CET)
From: SOME ONE <jk@localhost.localdomain>
To: ME <jk@localhost.localdomain>
Subject: Re: testing pgpenvelope reply + quoting

THIS IS SOMEONE's REPLY TO MY MESSAGE.
not using any pgp implementation. quoting my original message in
microsoft's way.

----Original Message----
From: ME <jk@localhost.localdomain>
To: SOME ONE <jk@localhost.localdomain>
Subject: testing pgpenvelope reply + quoting
Message-ID: <Pine.LNX.4.33.0112111800310.821-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

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

THIS IS MY ORIGINAL MESSAGE.
it is gpg signed w/ pgpenvolpe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iD8DBQE8FjwcY6Nk2Nv6ZRcRAlmFAJ9BrZNptkwlvDYWEbqShh4E7IrZLACeI5WW
o66WVq/pguTU/EJN1zeRRbM=
=CZj7
-----END PGP SIGNATURE-----

filtering this through pgpenvelop 2.9.0 results in:

Date: Tue, 11 Dec 2001 18:09:58 +0100 (CET)
From: SOME ONE <jk@localhost.localdomain>
To: ME <jk@localhost.localdomain>
Subject: Re: testing pgpenvelope reply + quoting

THIS IS SOMEONE's REPLY TO MY MESSAGE.
not using any pgp implementation. quoting my original message in
microsoft's way.

-----pgpenvelope processed message-----

THIS IS MY ORIGINAL MESSAGE.
it is gpg signed w/ pgpenvolpe

-----pgpenvelope information -----
Hash: SHA1
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

gpg: Signature made Tue Dec 11 18:02:20 2001 CET using DSA key ID DBFA6517
gpg: Good signature from "Jan Korger <jan@korger.de>"
gpg: aka "spacezone.de <jack@spacezone.de>"

pgpenvelope_decrypt: message processed at Tue Dec 11 18:09:59 2001

-----end pgpenvelope information -----

security hole: fake pgpenvolpe info

Anonymous — Sun, 06 May 2001 15:10:19 -0000

any one can send an email containing
-----pgpenvelope processed message-----
in the first line and at the end something like:
-----pgpenvelope information-----
Hash: SHA1
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

gpg: Signature made Sat May 5 21:01:58 2001 CEST using DSA key ID 336E127C
gpg: Good signature from "Jan Korger <JanKorger@bigfoot.com>"
gpg: aka "spacezone.de: Jan Korger <jack@spacezone.de>"

pgpenvelope_decrypt: message processed at Sun May 6 16:46:38 2001

-----end pgpenvelope information-----

those using the procmail part of pgpenveloüpe would probably never notice that it wasn't their pgpenvelope that created this message

bug in pine 4.32

captain larry — Thu, 22 Feb 2001 06:34:38 -0000

there is a bug in pine 4.32. this isn't pgpenvelope's fault but it would be worth documenting somewhere.

basically spaces and quote's no longer work inside the display-filter setting. this is broken (and fixed in 4.33) but it means that the documented filter:

_BEGINNING("-----BEGIN PGP ")_ /usr/local/bin/pgpenvelope_decrypt

no longer works and needs to be changed to:

_BEGINNING(-----BEGIN)_ /usr/local/bin/pgpenvelope_decrypt

adam.

pgpenvelope uses temporary files for pipes

Frank Tobin — Wed, 25 Oct 2000 08:12:27 -0000

pgpenvelope uses temporary files for both incoming and outgoing messages when talking with GnuPG, to deal with filled-buffer issues. It needs to be looked into if this is necessary.

duplicated incoming message blocks

Frank Tobin — Fri, 13 Oct 2000 10:23:09 -0000

When there is multiple PGP blocks in a message, pgpenvelope seems to do some strange stuff like duplicate some of the blocks. I need to look into this more.

encrypting large messaages fails

Frank Tobin — Sat, 30 Sep 2000 19:50:11 -0000

Encrypting large messages fails, very likely do to buffering/IO/pipe problems. This problem was solved for decrypting messages, but unfortunately not for encrypting.

encrypting to non-first secondary keys

Frank Tobin — Mon, 11 Sep 2000 20:46:23 -0000

By default, pgpenvelope encrypts to the first secondary key, if it exists. This needs to be changed so that the user can be prompted as to which secondary key he/she wants to encrypt to.

.pgpenvelope permissions problem....

Anonymous — Sun, 23 Jul 2000 07:34:32 -0000

Just installed pgpenvelope 2.8.10 on one of our mail servers for folks to use with pine, and discovered that people adding in the filter lines to pine end up with a .pgpenvelope directory in their homedir with permissions 000: d---------, meaning pgpenvelope can't write prefs.default in there.

Just FYI. Easy enough to fix by hand, but was a bit of a pain to track down.