* NEWS: Add notes about notation names and '@', the --trust-model option,

default algorithms from --personal-xxxx, --primary-keyring, changes with
--s2k-digest-algo, the new anonymous recipient improvements, and
non-optimized memory wiping.
This commit is contained in:
David Shaw 2002-11-26 04:02:58 +00:00
parent 29c83f1c60
commit 98708e1770
2 changed files with 36 additions and 0 deletions

View File

@ -1,3 +1,10 @@
2002-11-25 David Shaw <dshaw@jabberwocky.com>
* NEWS: Add notes about notation names and '@', the --trust-model
option, default algorithms from --personal-xxxx,
--primary-keyring, changes with --s2k-digest-algo, the new
anonymous recipient improvements, and non-optimized memory wiping.
2002-11-13 David Shaw <dshaw@jabberwocky.com>
* THANKS: Changes from stable branch.

29
NEWS
View File

@ -1,6 +1,35 @@
Noteworthy changes in version 1.3.2 (unreleased)
------------------------------------------------
* Notation names that do not contain a '@' are no longer allowed
unless --expert is set. This is to help prevent pollution of
the (as yet unused) IETF notation namespace.
* Multiple trust models are now supported via the --trust-model
option. The options are "openpgp" (web-of-trust plus trust
signatures), "classic" (web-of-trust only), and "always"
(identical to the --always-trust option).
* The --personal-{cipher|digest|compression}-preferences are now
consulted to get default algorithms before resorting to the
last-ditch defaults of --s2k-cipher-algo, SHA1, and ZIP
respectively. This allows a user to set algorithms to use in a
safe manner so they are used when legal to do so, without
forcing them on for all messages.
* New --primary-keyring option to designate the keyring that the
user wants new keys imported into.
* --s2k-digest-algo is now used for all password mangling.
Earlier versions used both --s2k-digest-algo and --digest-algo
for passphrase mangling.
* Handling of --hidden-recipient or --throw-keyid messages is now
easier - the user only needs to give their passphrase once, and
GnuPG will try it against all of the available secret keys.
* Care is taken to prevent compiler optimization from removing
memory wiping code.
Noteworthy changes in version 1.3.1 (2002-11-12)
------------------------------------------------