|
|
1.1 root 1: News for PGP 2.2
2:
3: The main change since PGP 2.1 is a speedup in key management, and
4: the ability to encrypt for more than one recipient. Apart from
5: this there are some bugfixes and some new options to make it easier
6: to use PGP from shell scripts or mailers.
7:
8: You can encrypt for more than one recipient by specifying additional
9: userids on the command line eg:
10:
11: pgp -e plaintext Alice Bob Carol
12:
13:
14: Some notes about the changes:
15:
16: - PGP doesn't do a keycheck on a keyfile before it is added anymore,
17: this is to speed up merging a big keyfile with your public keyring which
18: may already have most of the keys in the keyfile you are adding. After
19: PGP has checked a signature it sets a flag in your public keyring to
20: mark this signature as checked. Because PGP 2.1 didn't have these
21: flags, PGP will check *all* signatures on your keyring the first time
22: you add a key with PGP 2.2. After that PGP will only check new
23: signatures. Also by using an older version than 2.2 on your keyring you
24: will clear these flags again.
25:
26:
27: New options:
28:
29: +interactive
30: If you add a keyfile, PGP will ask for each new key if it should
31: be added to your keyring.
32:
33: Options for use in shell scripts:
34:
35: +verbose=n
36: The default is 1. With +verbose=0, PGP will only print an error
37: message if something goes wrong. With +verbose=2, PGP will tell
38: you what it's doing in detail suitable for debugging.
39:
40: +force
41: Overwrite output file without asking, or with -kr: remove key
42: without asking (only if it has just one userid).
43:
44: +batchmode
45: With this option PGP won't ask any questions or prompt for
46: alternate file names. Some of the key commands still need
47: user interaction and can't be done from a shell script.
48: You can also use this option to check if a file has a good
49: signature. If the input file did not have a signature the exit
50: code will be 1, if the file had a signature and if it checked OK
51: the exit code will be 0. Note that if the input file has more
52: than one armored messages, a good signature on one of these
53: messages will make the exit code 0 (if there are no errors).
54:
55: These "long" options can be abbreviated as long as the abbreviation is
56: unambiguous. "interactive" and "verbose" can also be set in config.txt;
57: you can then turn these flags off on the command line with +option=.
58:
59:
60: Some of the bug fixes:
61:
62: - Key lookup on keyID (eg 0x12AB) fixed for -ks/-krs.
63:
64: - Dearmoring of Macintosh type text files (CR only) now also works.
65:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.