DANE CHANGES

Reviewed-by: Richard Levitte <levitte@openssl.org>

diff --git a/CHANGES b/CHANGES
index b5a9e1e9671ef7d671a0599e0c57f09e3f9f1128..4e305721e38aaf10094be3a874c28894a89e9a7d 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -4,6 +4,20 @@
 
  Changes between 1.0.2e and 1.1.0  [xx XXX xxxx]
 
+  *) Support for RFC6698/RFC7671 DANE TLSA peer authentication.
+
+     Obtaining and performing DNSSEC validation of TLSA records is
+     the application's responsibility.  The application provides
+     the TLSA records of its choice to OpenSSL, and these are then
+     used to authenticate the peer.
+
+     The TLSA records need not even come from DNS.  They can, for
+     example, be used to implement local end-entity certificate or
+     trust-anchor "pinning", where the "pin" data takes the form
+     of TLSA records, which can augment or replace verification
+     based on the usual WebPKI public certification authorities.
+     [Viktor Dukhovni]
+
   *) Revert default OPENSSL_NO_DEPRECATED setting.  Instead OpenSSL
      continues to support deprecated interfaces in default builds.
      However, applications are strongly advised to compile their

diff --git a/NEWS b/NEWS
index 13e1a91c3ff4a5440c7e77ca6b42030a9bc30b7b..17fee47edc2d4e40f80c77104ad2daf7f9ca2fd3 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -28,6 +28,7 @@
         argument, or via the "--api=1.1.0|1.0.0|0.9.8" option.
       o Application software can be compiled with -DOPENSSL_API_COMPAT=version
         to ensure that features deprecated before that version are not exposed.
+      o Support for RFC6698/RFC7671 DANE TLSA peer authentication
 
   Major changes between OpenSSL 1.0.2d and OpenSSL 1.0.2e [3 Dec 2015]