|
|
1.1 root 1: To integrate PGP 2.1 with Elm and NN:
2:
3: 0) Make sure the path of Perl in the first line of each of the three
4: files reflects the full path of this utility for your system. Also,
5: make sure that the EDITOR and PAGER environment variables reflect your
6: editor and pager of choice (vi and less will be used by default).
7:
8: 1) Put the files morepgp, mailpgp, and postpgp in one of the
9: directories on your PATH.
10:
11: 2) Modify your ~/.elm/elmrc file to contain the following lines:
12:
13: editor = mailpgp
14: pager = morepgp
15:
16: 3) Modify your ~/.nn/init file to contain the following lines:
17:
18: set editor postpgp
19:
20: That's all folks! Now, each time you post a message or reply to a
21: message with nn, after you exit your editor, you will be asked whether
22: you want to sign your message. Each time you compose a private message
23: with elm, or reply to a message, and leave the editor, you'll be asked
24: whether you want to sign and/or encrypt the message. When you browse a
25: message, if it contains any PGP blocks, those will be properly
26: interpreted. When you reply to a message containing PGP blocks, you'll
27: have them properly decrypted and quoted in your editor.
28:
29: BUGS
30:
31: 1) You cannot encrypt messages that you mail from nn. You can only
32: sign them.
33:
34: 2) When you reply to a PGP-encryted message, the encrypted message is
35: temporarily kept on the disk, which is a security hole.
36:
37: 3) The temporary files are not wiped out, they are just deleted.
38:
39: 4) The scripts are ugly, reflecting my lack of knowledge of Perl. In
40: fact, I don't know Perl at all; I hacked somebody else's scripts. If
41: you know Perl better then me, please feel free to improve the scripts
42: and don't forget to mail me a copy of the improved version.
43:
44: I can be contacted as Vesselin Bontchev at
45: [email protected]
46:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.