[svn] GnuPG - r4041 - trunk

[svn author dshaw]

Author: dshaw
Date: 2006-03-07 17:20:03 +0100 (Tue, 07 Mar 2006)
New Revision: 4041

Modified:
   trunk/ChangeLog
   trunk/NEWS
Log:
* NEWS: Note --auto-key-locate and that keyservers can handle binary data
now.


Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog	2006-03-07 11:05:41 UTC (rev 4040)
+++ trunk/ChangeLog	2006-03-07 16:20:03 UTC (rev 4041)
@@ -1,3 +1,8 @@
+2006-03-07  David Shaw  <dshaw at jabberwocky.com>
+
+	* NEWS: Note --auto-key-locate and that keyservers can handle
+	binary data now.
+
 2006-03-01  David Shaw  <dshaw at jabberwocky.com>
 
 	* configure.ac: Fix accidental enabling of SHA-384/512.  Noted by

Modified: trunk/NEWS
===================================================================
--- trunk/NEWS	2006-03-07 11:05:41 UTC (rev 4040)
+++ trunk/NEWS	2006-03-07 16:20:03 UTC (rev 4041)
@@ -51,13 +51,23 @@
       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)
 ------------------------------------------------