File: README

package info (click to toggle)
pgp4pine 1.71b-5
  • links: PTS
  • area: contrib
  • in suites: potato
  • size: 416 kB
  • ctags: 120
  • sloc: ansic: 1,891; sh: 327; makefile: 81
file content (48 lines) | stat: -rw-r--r-- 1,931 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
PGP4Pine 1.7

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 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'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 2.6.3i (PGP2), and GPG
0.9x (GPG). If you want to use multiple versions, set up seperate profiles.

	Quick Note
BTW, I found out there is a Perl script and a shell script that are both
called pgp4pine floating around. Although we both do the same basic stuff,
mine is in C, and theirs in Perl/shellscript. Also, I support PGP2, PGP5, 
and GPG.

	Installation
./configure && make && make 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".