Re: test wip/pine-pgp-filters ?

On Fri, 7 May 2004, Jeremy C. Reed wrote:

: The pgp tools included with the pkgsrc pine package are old (not updated)
: and insecure.
:
: I have packaged wip/pine-pgp-filters but have not tested yet.
:
: It is said to work with pgp6 (which is why I cc'd tv) and gpg.

Note:  wip/pgp6 is not in main pkgsrc because it coredumps a lot.  sigh.

: pkgsrc already has pinepgp too (which is why I cc'd jschauma).

And pkgsrc-wip has pgpenvelope, which I use.  But if pine-pgp-filters is
better, I may switch.  :)

: Should I use the same PINEPGP_USEGPG and PINEPGP_USEPGP5 for my package
: too?

These should really be renamed something like USE_GNUPG and USE_PGP5 so they
can have effect elsewhere.  Additionally, USE_PGP5 should always default to
"no".  It's old, outmoded, and is not very interoperability-friendly.  It
only works well with PGP 5.x, 6.5+ (not 6.0!), and gnupg (but only if
messages *from* gnupg used --pgp5 at sign or encrypt time; from pgp5 to
gnupg works by default).

I recommend gnupg with USE_IDEA enabled.  If you need send-to-pgp-2.x
interoperability, install pgp2 separately until the gnupg folks get their
panties out of a knot and fix --pgp2 to DTRT when signing and/or encrypting.
(I'm going to be opening bug entries on the relevant issues on
bugs.gnupg.org soon.)

-- 
-- Todd Vierling <tv@xxxxxxx> <tv@xxxxxxxxx>


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3