From aca9f9ab5a8790f2b0656c78b08bec6c7d9abd62 Mon Sep 17 00:00:00 2001
From: Martin Willi <martin@strongswan.org>
Date: Thu, 7 Jan 2010 16:16:22 +0100
Subject: [PATCH] Added NEWS about mutual EAP-only authentication

---
 NEWS | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/NEWS b/NEWS
index 64801421f..3fcb49c2a 100644
--- a/NEWS
+++ b/NEWS
@@ -35,6 +35,12 @@ strongswan-4.3.6
   "charon.send_vendor_id" option in strongswan.conf to let the remote peer know
   this is the case.
 
+- Experimental support for draft-eronen-ipsec-ikev2-eap-auth, where the
+  responder omits public key authentication in favor of a mutual authentication
+  method. To enable EAP-only authentication, set rightauth=eap on the responder
+  to rely only on the MSK constructed AUTH payload. This not-yet standardized
+  extension requires the strongSwan vendor ID introduced above.
+
 - The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus
   allowing interoperability.