security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-22 10:19:57 +01:00
Code Activity

* NEWS: Note --auto-key-locate and that keyservers can handle binary data

Browse Source 
now.
This commit is contained in:
David Shaw 2006-03-07 16:20:03 +00:00
parent 4aeb4d4b10
commit 81e2591421
2 changed files with 19 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2006-03-07 David Shaw <dshaw@jabberwocky.com>
* NEWS: Note --auto-key-locate and that keyservers can handle
binary data now.
2006-03-01 David Shaw <dshaw@jabberwocky.com>
* configure.ac: Fix accidental enabling of SHA-384/512. Noted by

18
NEWS
View File

@ -51,11 +51,21 @@ Noteworthy changes in version 1.4.3
are HTTP and finger, plus anything that cURL supplies, if built
with cURL support.
* Files containing several signed messages are not anymore allowed
because there is no clean way to report the status of such files
back to the caller. To partly revert to the old behaviour the
new option --allow-multisig-verification may be used.
* Files containing several signed messages are not allowed any
longer as there is no clean way to report the status of such
files back to the caller. To partly revert to the old behaviour
the new option --allow-multisig-verification may be used.
* The keyserver helpers can now handle keys in either ASCII armor
or binary format.
* New auto-key-locate option that takes an ordered list of methods
to locate a key if it is not available at encryption time (-r or
--recipient). Possible methods include "cert" (use DNS CERT as
per RFC2538bis, "pka" (use DNS PKA), "ldap" (consult the LDAP
server for the domain in question), "keyserver" (use the
currently defined keyserver), as well as arbitrary keyserver
URIs that will be contacted for the key.
Noteworthy changes in version 1.4.2 (2005-07-26)