PGP4Pine 1.76

If you're compiling: READ THE INSTALL FILE!!!!!!!!!!!!!

*** PLEASE *** edit your ~/.pgp4pinerc file once you have one and use a 
profile_*_tempfile variable! Esp. with GnuPG it helps. Make sure the
directory has permissons of 0700!

As of 1.60, if you want back the double-enter
sequence, add extra_enter_at_end=1 to your .pgp4pinerc file.

As of 1.55, PGP 2 only supports the default keyring files. PGP 5/6 and GnuPG
support whatever keyring you define in their preferences, by default the defaults.

As of 1.54, I've removed the option pgpFolder in the pgp4pinerc file. I now
use the full path for pgpv/pgpe/pgps/pgpk/pgp/gpg executables, it's safer.

	2038/Y2K/Y10K-compatibility
Although MY program doesn't use dates, I dunno if Pine is Y2K/Y10K/2038
compliant. I heard Pine 3 is not. I'd suggest going to 
http://www.washington.edu/pine and seeing for yourself. BTW, before 2038, 
make sure you're on 64-bit UNIX and recompile this program under that. 
This is not a legal statement concerning anything, especially Year 2000 
Readiness, nor should it be taken as such. For a full Y2K audit of this 
program, please hire a programer yourself.

	PGP-compatibility
This program should work with PGP 5.0 (PGP5), PGP 6.5 (PGP6), PGP 2.6.3i 
(PGP2), and GPG 1.x (GPG). If you want to use multiple versions, set up 
seperate profiles.

	Quick Note
BTW, I found out there is lots of stuff called pgp4pine floating around. 
Although all do the same basic stuff, they are totally different.
I find mine the most advanced, but maybe you like it simple.

	Quick Installation
./configure && make && make install && cat INSTALL

	Defaults
The package comes presetup for PGP 5 with a temporary file of 
$(HOME)/pgp4pine.tmp

	Security
Okay, I'm currently in progress of security auditing pgp4pine. (For buffer
overflows and stuff.) Files with // SECURITY OKAY should be fine.
Also, for the truely paranoid, don't define NCURSES_OKAY, I arbitrarily
call "clear".
