denozord/strongswan-ext
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added NEWS for the new Vendor ID requirement for private use allocations

Browse Source
This commit is contained in:
Martin Willi
2010-01-07 11:14:33 +01:00
parent 023fd8f135
commit cdad91de49
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
NEWS
+7 -1
View File
@@ -1,7 +1,7 @@
strongswan-4.3.6 strongswan-4.3.6
---------------- ----------------
- The IKEv2 daemon supports RFC 3779 IP address block constraints - The IKEv2 daemon supports RFC 3779 IP address block constraints
carried as a critical X.509v3 extension in the peer certificate. carried as a critical X.509v3 extension in the peer certificate.
- The ipsec pool --add|del dns|nbns command manages DNS and NBNS name - The ipsec pool --add|del dns|nbns command manages DNS and NBNS name
@@ -29,6 +29,12 @@ strongswan-4.3.6
- Fixed BEET mode connections on recent kernels by installing SAs with - Fixed BEET mode connections on recent kernels by installing SAs with
appropriate traffic selectors, based on a patch by Michael Rossberg. appropriate traffic selectors, based on a patch by Michael Rossberg.
- Using extensions (such as BEET mode) and crypto algorithms (such as twofish,
serpent, sha256_96) allocated in the private use space now require that we
know its meaning, i.e. we are talking to strongSwan. Use the new
"charon.send_vendor_id" option in strongswan.conf to let the remote peer know
this is the case.
- The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus - The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus
allowing interoperability. allowing interoperability.