4 - Full X.509 certificate trust chain verification has been implemented.
5 End entity certificates can be exchanged via CERT payloads. The current
6 default is leftsendcert=always, since CERTREQ payloads are not supported
7 yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls.
9 - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2
10 would offer more possibilities for traffic selection, but the Linux kernel
11 currently does not support it. That's why we stick with these simple
12 ipsec.conf rules for now.
14 - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no
15 IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear,
18 - Initial NAT traversal support in IKEv2. Charon includes NAT detection
19 notify payloads to detect NAT routers between the peers. It switches
20 to port 4500, uses UDP encapsulated ESP packets, handles peer address
21 changes gracefully and sends keep alive message periodically.
23 - Reimplemented IKE_SA state machine for charon, which allows simultaneous
24 rekeying, more shared code, cleaner design, proper retransmission
25 and a more extensible code base.
27 - The mixed PSK/RSA roadwarrior detection capability introduced by the
28 strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal
29 payloads by the responder right before any defined IKE Main Mode state had
30 been established. Although any form of bad proposal syntax was being correctly
31 detected by the payload parser, the subsequent error handler didn't check
32 the state pointer before logging current state information, causing an
33 immediate crash of the pluto keying daemon due to a NULL pointer.
39 - Added algorithm selection to charon: New default algorithms for
40 ike=aes128-sha-modp2048, as both daemons support it. The default
41 for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles
42 the ike/esp parameter the same way as pluto. As this syntax does
43 not allow specification of a pseudo random function, the same
44 algorithm as for integrity is used (currently sha/md5). Supported
46 Encryption: aes128, aes192, aes256
47 Integrity/PRF: md5, sha (using hmac)
48 DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192
50 Encryption: aes128, aes192, aes256, 3des, blowfish128,
51 blowfish192, blowfish256
53 More IKE encryption algorithms will come after porting libcrypto into
56 - initial support for rekeying CHILD_SAs using IKEv2. Currently no
57 perfect forward secrecy is used. The rekeying parameters rekey,
58 rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported
59 when using IKEv2. WARNING: charon currently is unable to handle
60 simultaneous rekeying. To avoid such a situation, use a large
61 rekeyfuzz, or even better, set rekey=no on one peer.
63 - support for host2host, net2net, host2net (roadwarrior) tunnels
64 using predefined RSA certificates (see uml scenarios for
65 configuration examples).
67 - new build environment featuring autotools. Features such
68 as HTTP, LDAP and smartcard support may be enabled using
69 the ./configure script. Changing install directories
70 is possible, too. See ./configure --help for more details.
72 - better integration of charon with ipsec starter, which allows
73 (almost) transparent operation with both daemons. charon
74 handles ipsec commands up, down, status, statusall, listall,
75 listcerts and allows proper load, reload and delete of connections
81 - initial support of the IKEv2 protocol. Connections in
82 ipsec.conf designated by keyexchange=ikev2 are negotiated
83 by the new IKEv2 charon keying daemon whereas those marked
84 by keyexchange=ikev1 or the default keyexchange=ike are
85 handled thy the IKEv1 pluto keying daemon. Currently only
86 a limited subset of functions are available with IKEv2
87 (Default AES encryption, authentication based on locally
88 imported X.509 certificates, unencrypted private RSA keys
89 in PKCS#1 file format, limited functionality of the ipsec
96 - the dynamic iptables rules from the _updown_x509 template
97 for KLIPS and the _updown_policy template for NETKEY have
98 been merged into the default _updown script. The existing
99 left|rightfirewall keyword causes the automatic insertion
100 and deletion of ACCEPT rules for tunneled traffic upon
101 the successful setup and teardown of an IPsec SA, respectively.
102 left|rightfirwall can be used with KLIPS under any Linux 2.4
103 kernel or with NETKEY under a Linux kernel version >= 2.6.16
104 in conjuction with iptables >= 1.3.5. For NETKEY under a Linux
105 kernel version < 2.6.16 which does not support IPsec policy
106 matching yet, please continue to use a copy of the _updown_espmark
107 template loaded via the left|rightupdown keyword.
109 - a new left|righthostaccess keyword has been introduced which
110 can be used in conjunction with left|rightfirewall and the
111 default _updown script. By default leftfirewall=yes inserts
112 a bi-directional iptables FORWARD rule for a local client network
113 with a netmask different from 255.255.255.255 (single host).
114 This does not allow to access the VPN gateway host via its
115 internal network interface which is part of the client subnet
116 because an iptables INPUT and OUTPUT rule would be required.
117 lefthostaccess=yes will cause this additional ACCEPT rules to
120 - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal
121 payload is preparsed in order to find out whether the roadwarrior
122 requests PSK or RSA so that a matching connection candidate can
129 - the new _updown_policy template allows ipsec policy based
130 iptables firewall rules. Required are iptables version
131 >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes
132 the _updown_espmark template, so that no INPUT mangle rules
133 are required any more.
135 - added support of DPD restart mode
137 - ipsec starter now allows the use of wildcards in include
138 statements as e.g. in "include /etc/my_ipsec/*.conf".
139 Patch courtesy of Matthias Haas.
141 - the Netscape OID 'employeeNumber' is now recognized and can be
142 used as a Relative Distinguished Name in certificates.
148 - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec
149 command and not of ipsec setup any more.
151 - ipsec starter now supports AH authentication in conjunction with
152 ESP encryption. AH authentication is configured in ipsec.conf
153 via the auth=ah parameter.
155 - The command ipsec scencrypt|scdecrypt <args> is now an alias for
156 ipsec whack --scencrypt|scdecrypt <args>.
158 - get_sa_info() now determines for the native netkey IPsec stack
159 the exact time of the last use of an active eroute. This information
160 is used by the Dead Peer Detection algorithm and is also displayed by
161 the ipsec status command.
167 - running under the native Linux 2.6 IPsec stack, the function
168 get_sa_info() is called by ipsec auto --status to display the current
169 number of transmitted bytes per IPsec SA.
171 - get_sa_info() is also used by the Dead Peer Detection process to detect
172 recent ESP activity. If ESP traffic was received from the peer within
173 the last dpd_delay interval then no R_Y_THERE notification must be sent.
175 - strongSwan now supports the Relative Distinguished Name "unstructuredName"
176 in ID_DER_ASN1_DN identities. The following notations are possible:
178 rightid="unstructuredName=John Doe"
179 rightid="UN=John Doe"
181 - fixed a long-standing bug which caused PSK-based roadwarrior connections
182 to segfault in the function id.c:same_id() called by keys.c:get_secret()
183 if an FQDN, USER_FQDN, or Key ID was defined, as in the following example.
190 - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall).
192 - ipsec starter didn't set host_addr and client.addr ports in whack msg.
194 - in order to guarantee backwards-compatibility with the script-based
195 auto function (e.g. auto --replace), the ipsec starter scripts stores
196 the defaultroute information in the temporary file /var/run/ipsec.info.
198 - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH
199 Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config
202 - the ipsec starter now also recognizes the parameters authby=never and
203 type=passthrough|pass|drop|reject.
209 - ipsec starter now supports the also parameter which allows
210 a modular structure of the connection definitions. Thus
211 "ipsec start" is now ready to replace "ipsec setup".
217 - Mathieu Lafon's popular ipsec starter tool has been added to the
218 strongSwan distribution. Many thanks go to Stephan Scholz from astaro
219 for his integration work. ipsec starter is a C program which is going
220 to replace the various shell and awk starter scripts (setup, _plutoload,
221 _plutostart, _realsetup, _startklips, _confread, and auto). Since
222 ipsec.conf is now parsed only once, the starting of multiple tunnels is
223 accelerated tremedously.
225 - Added support of %defaultroute to the ipsec starter. If the IP address
226 changes, a HUP signal to the ipsec starter will automatically
227 reload pluto's connections.
229 - moved most compile time configurations from pluto/Makefile to
230 Makefile.inc by defining the options USE_LIBCURL, USE_LDAP,
231 USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE.
233 - removed the ipsec verify and ipsec newhostkey commands
235 - fixed some 64-bit issues in formatted print statements
237 - The scepclient functionality implementing the Simple Certificate
238 Enrollment Protocol (SCEP) is nearly complete but hasn't been
245 - CA certicates are now automatically loaded from a smartcard
246 or USB crypto token and appear in the ipsec auto --listcacerts
253 - when using "ipsec whack --scencrypt <data>" with a PKCS#11
254 library that does not support the C_Encrypt() Cryptoki
255 function (e.g. OpenSC), the RSA encryption is done in
256 software using the public key fetched from the smartcard.
258 - The scepclient function now allows to define the
259 validity of a self-signed certificate using the --days,
260 --startdate, and --enddate options. The default validity
261 has been changed from one year to five years.
267 - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11
268 interface to other applications for RSA encryption and decryption
269 via the whack interface. Notation:
271 ipsec whack --scencrypt <data>
272 [--inbase 16|hex|64|base64|256|text|ascii]
273 [--outbase 16|hex|64|base64|256|text|ascii]
276 ipsec whack --scdecrypt <data>
277 [--inbase 16|hex|64|base64|256|text|ascii]
278 [--outbase 16|hex|64|base64|256|text|ascii]
281 The default setting for inbase and outbase is hex.
283 The new proxy interface can be used for securing symmetric
284 encryption keys required by the cryptoloop or dm-crypt
285 disk encryption schemes, especially in the case when
286 pkcs11keepstate=yes causes pluto to lock the pkcs11 slot
289 - if the file /etc/ipsec.secrets is lacking during the startup of
290 pluto then the root-readable file /etc/ipsec.d/private/myKey.der
291 containing a 2048 bit RSA private key and a matching self-signed
292 certificate stored in the file /etc/ipsec.d/certs/selfCert.der
293 is automatically generated by calling the function
295 ipsec scepclient --out pkcs1 --out cert-self
297 scepclient was written by Jan Hutter and Martin Willi, students
298 at the University of Applied Sciences in Rapperswil, Switzerland.
304 - the current extension of the PKCS#7 framework introduced
305 a parsing error in PKCS#7 wrapped X.509 certificates that are
306 e.g. transmitted by Windows XP when multi-level CAs are used.
307 the parsing syntax has been fixed.
309 - added a patch by Gerald Richter which tolerates multiple occurrences
310 of the ipsec0 interface when using KLIPS.
316 - with gawk-3.1.4 the word "default2 has become a protected
317 keyword for use in switch statements and cannot be used any
318 more in the strongSwan scripts. This problem has been
319 solved by renaming "default" to "defaults" and "setdefault"
320 in the scripts _confread and auto, respectively.
322 - introduced the parameter leftsendcert with the values
324 always|yes (the default, always send a cert)
325 ifasked (send the cert only upon a cert request)
326 never|no (never send a cert, used for raw RSA keys and
329 - fixed the initialization of the ESP key length to a default of
330 128 bits in the case that the peer does not send a key length
331 attribute for AES encryption.
333 - applied Herbert Xu's uniqueIDs patch
335 - applied Herbert Xu's CLOEXEC patches
341 - CRLs can now be cached also in the case when the issuer's
342 certificate does not contain a subjectKeyIdentifier field.
343 In that case the subjectKeyIdentifier is computed by pluto as the
344 160 bit SHA-1 hash of the issuer's public key in compliance
345 with section 4.2.1.2 of RFC 3280.
347 - Fixed a bug introduced by strongswan-2.5.1 which eliminated
348 not only multiple Quick Modes of a given connection but also
349 multiple connections between two security gateways.
355 - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute
356 installed either by setting auto=route in ipsec.conf or by
357 a connection put into hold, generates an XFRM_AQUIRE event
358 for each packet that wants to use the not-yet exisiting
359 tunnel. Up to now each XFRM_AQUIRE event led to an entry in
360 the Quick Mode queue, causing multiple IPsec SA to be
361 established in rapid succession. Starting with strongswan-2.5.1
362 only a single IPsec SA is established per host-pair connection.
364 - Right after loading the PKCS#11 module, all smartcard slots are
365 searched for certificates. The result can be viewed using
368 ipsec auto --listcards
370 The certificate objects found in the slots are numbered
371 starting with #1, #2, etc. This position number can be used to address
372 certificates (leftcert=%smartcard) and keys (: PIN %smartcard)
373 in ipsec.conf and ipsec.secrets, respectively:
375 %smartcard (selects object #1)
376 %smartcard#1 (selects object #1)
377 %smartcard#3 (selects object #3)
379 As an alternative the existing retrieval scheme can be used:
381 %smartcard:45 (selects object with id=45)
382 %smartcard0 (selects first object in slot 0)
383 %smartcard4:45 (selects object in slot 4 with id=45)
385 - Depending on the settings of CKA_SIGN and CKA_DECRYPT
386 private key flags either C_Sign() or C_Decrypt() is used
387 to generate a signature.
389 - The output buffer length parameter siglen in C_Sign()
390 is now initialized to the actual size of the output
391 buffer prior to the function call. This fixes the
392 CKR_BUFFER_TOO_SMALL error that could occur when using
393 the OpenSC PKCS#11 module.
395 - Changed the initialization of the PKCS#11 CK_MECHANISM in
396 C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }.
398 - Refactored the RSA public/private key code and transferred it
399 from keys.c to the new pkcs1.c file as a preparatory step
400 towards the release of the SCEP client.
406 - The loading of a PKCS#11 smartcard library module during
407 runtime does not require OpenSC library functions any more
408 because the corresponding code has been integrated into
409 smartcard.c. Also the RSAREF pkcs11 header files have been
410 included in a newly created pluto/rsaref directory so that
411 no external include path has to be defined any longer.
413 - A long-awaited feature has been implemented at last:
414 The local caching of CRLs fetched via HTTP or LDAP, activated
415 by the parameter cachecrls=yes in the config setup section
416 of ipsec.conf. The dynamically fetched CRLs are stored under
417 a unique file name containing the issuer's subjectKeyID
418 in /etc/ipsec.d/crls.
420 - Applied a one-line patch courtesy of Michael Richardson
421 from the Openswan project which fixes the kernel-oops
422 in KLIPS when an snmp daemon is running on the same box.
428 - Eliminated null length CRL distribution point strings.
430 - Fixed a trust path evaluation bug introduced with 2.4.3
436 - Improved the joint OCSP / CRL revocation policy.
437 OCSP responses have precedence over CRL entries.
439 - Introduced support of CRLv2 reason codes.
441 - Fixed a bug with key-pad equipped readers which caused
442 pluto to prompt for the pin via the console when the first
443 occasion to enter the pin via the key-pad was missed.
445 - When pluto is built with LDAP_V3 enabled, the library
446 liblber required by newer versions of openldap is now
453 - Added the _updown_espmark template which requires all
454 incoming ESP traffic to be marked with a default mark
457 - Introduced the pkcs11keepstate parameter in the config setup
458 section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11
459 session and login states are kept as long as possible during
460 the lifetime of pluto. This means that a PIN entry via a key
461 pad has to be done only once.
463 - Introduced the pkcs11module parameter in the config setup
464 section of ipsec.conf which specifies the PKCS#11 module
465 to be used with smart cards. Example:
467 pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo
469 - Added support of smartcard readers equipped with a PIN pad.
471 - Added patch by Jay Pfeifer which detects when netkey
472 modules have been statically built into the Linux 2.6 kernel.
474 - Added two patches by Herbert Xu. The first uses ip xfrm
475 instead of setkey to flush the IPsec policy database. The
476 second sets the optional flag in inbound IPComp SAs only.
478 - Applied Ulrich Weber's patch which fixes an interoperability
479 problem between native IPsec and KLIPS systems caused by
480 setting the replay window to 32 instead of 0 for ipcomp.
486 - Fixed a bug which caused an unwanted Mode Config request
487 to be initiated in the case where "right" was used to denote
488 the local side in ipsec.conf and "left" the remote side,
489 contrary to the recommendation that "right" be remote and
496 - updated Vendor ID to strongSwan-2.4.0
498 - updated copyright statement to include David Buechi and
505 - strongSwan now communicates with attached smartcards and
506 USB crypto tokens via the standardized PKCS #11 interface.
507 By default the OpenSC library from www.opensc.org is used
508 but any other PKCS#11 library could be dynamically linked.
509 strongSwan's PKCS#11 API was implemented by David Buechi
510 and Michael Meier, both graduates of the Zurich University
511 of Applied Sciences in Winterthur, Switzerland.
513 - When a %trap eroute is triggered by an outgoing IP packet
514 then the native IPsec stack of the Linux 2.6 kernel [often/
515 always?] returns an XFRM_ACQUIRE message with an undefined
516 protocol family field and the connection setup fails.
517 As a workaround IPv4 (AF_INET) is now assumed.
519 - the results of the UML test scenarios are now enhanced
520 with block diagrams of the virtual network topology used
521 in a particular test.
527 - fixed IV used to decrypt informational messages.
528 This bug was introduced with Mode Config functionality.
530 - fixed NCP Vendor ID.
532 - undid one of Ulrich Weber's maximum udp size patches
533 because it caused a segmentation fault with NAT-ed
536 - added UML scenarios wildcards and attr-cert which
537 demonstrate the implementation of IPsec policies based
538 on wildcard parameters contained in Distinguished Names and
539 on X.509 attribute certificates, respectively.
545 - Added basic Mode Config functionality
547 - Added Mathieu Lafon's patch which upgrades the status of
548 the NAT-Traversal implementation to RFC 3947.
550 - The _startklips script now also loads the xfrm4_tunnel
553 - Added Ulrich Weber's netlink replay window size and
554 maximum udp size patches.
556 - UML testing now uses the Linux 2.6.10 UML kernel by default.
562 - Eric Marchionni and Patrik Rayo, both recent graduates from
563 the Zuercher Hochschule Winterthur in Switzerland, created a
564 User-Mode-Linux test setup for strongSwan. For more details
565 please read the INSTALL and README documents in the testing
568 - Full support of group attributes based on X.509 attribute
569 certificates. Attribute certificates can be generated
570 using the openac facility. For more details see
574 The group attributes can be used in connection definitions
575 in order to give IPsec access to specific user groups.
576 This is done with the new parameter left|rightgroups as in
578 rightgroups="Research, Sales"
580 giving access to users possessing the group attributes
581 Research or Sales, only.
583 - In Quick Mode clients with subnet mask /32 are now
584 coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should
585 fix rekeying problems with the SafeNet/SoftRemote and NCP
586 Secure Entry Clients.
588 - Changed the defaults of the ikelifetime and keylife parameters
589 to 3h and 1h, respectively. The maximum allowable values are
590 now both set to 24 h.
592 - Suppressed notification wars between two IPsec peers that
593 could e.g. be triggered by incorrect ISAKMP encryption.
595 - Public RSA keys can now have identical IDs if either the
596 issuing CA or the serial number is different. The serial
597 number of a certificate is now shown by the command
599 ipsec auto --listpubkeys
605 - Added Tuomo Soini's sourceip feature which allows a strongSwan
606 roadwarrior to use a fixed Virtual IP (see README section 2.6)
607 and reduces the well-known four tunnel case on VPN gateways to
608 a single tunnel definition (see README section 2.4).
610 - Fixed a bug occuring with NAT-Traversal enabled when the responder
611 suddenly turns initiator and the initiator cannot find a matching
612 connection because of the floated IKE port 4500.
614 - Removed misleading ipsec verify command from barf.
616 - Running under the native IP stack, ipsec --version now shows
617 the Linux kernel version (courtesy to the Openswan project).
623 - Introduced the ipsec auto --listalgs monitoring command which lists
624 all currently registered IKE and ESP algorithms.
626 - Fixed a bug in the ESP algorithm selection occuring when the strict flag
627 is set and the first proposed transform does not match.
629 - Fixed another deadlock in the use of the lock_certs_and_keys() mutex,
630 occuring when a smartcard is present.
632 - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event.
634 - Fixed the printing of the notification names (null)
636 - Applied another of Herbert Xu's Netlink patches.
642 - Support of Dead Peer Detection. The connection parameter
646 activates DPD for the given connection.
648 - The default Opportunistic Encryption (OE) policy groups are not
649 automatically included anymore. Those wishing to activate OE can include
650 the policy group with the following statement in ipsec.conf:
652 include /etc/ipsec.d/examples/oe.conf
654 The default for [right|left]rsasigkey is now set to %cert.
656 - strongSwan now has a Vendor ID of its own which can be activated
657 using the compile option VENDORID
659 - Applied Herbert Xu's patch which sets the compression algorithm correctly.
661 - Applied Herbert Xu's patch fixing an ESPINUDP problem
663 - Applied Herbert Xu's patch setting source/destination port numbers.
665 - Reapplied one of Herbert Xu's NAT-Traversal patches which got
666 lost during the migration from SuperFreeS/WAN.
668 - Fixed a deadlock in the use of the lock_certs_and_keys() mutex.
670 - Fixed the unsharing of alg parameters when instantiating group
677 - Thomas Walpuski made me aware of a potential DoS attack via
678 a PKCS#7-wrapped certificate bundle which could overwrite valid CA
679 certificates in Pluto's authority certificate store. This vulnerability
680 was fixed by establishing trust in CA candidate certificates up to a
681 trusted root CA prior to insertion into Pluto's chained list.
683 - replaced the --assign option by the -v option in the auto awk script
684 in order to make it run with mawk under debian/woody.
690 - Split of the status information between ipsec auto --status (concise)
691 and ipsec auto --statusall (verbose). Both commands can be used with
692 an optional connection selector:
694 ipsec auto --status[all] <connection_name>
696 - Added the description of X.509 related features to the ipsec_auto(8)
699 - Hardened the ASN.1 parser in debug mode, especially the printing
700 of malformed distinguished names.
702 - The size of an RSA public key received in a certificate is now restricted to
704 512 bits <= modulus length <= 8192 bits.
706 - Fixed the debug mode enumeration.
712 - Fixed another PKCS#7 vulnerability which could lead to an
713 endless loop while following the X.509 trust chain.
719 - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski
720 that accepted end certificates having identical issuer and subject
721 distinguished names in a multi-tier X.509 trust chain.
727 - Removed all remaining references to ipsec_netlink.h in KLIPS.
733 - The new "ca" section allows to define the following parameters:
736 cacert=koolCA.pem # cacert of kool CA
737 ocspuri=http://ocsp.kool.net:8001 # ocsp server
738 ldapserver=ldap.kool.net # default ldap server
739 crluri=http://www.kool.net/kool.crl # crl distribution point
740 crluri2="ldap:///O=Kool, C= .." # crl distribution point #2
741 auto=add # add, ignore
743 The ca definitions can be monitored via the command
745 ipsec auto --listcainfos
747 - Fixed cosmetic corruption of /proc filesystem by integrating
748 D. Hugh Redelmeier's freeswan-2.06 kernel fixes.
754 - Added support for the 818043 NAT-Traversal update of Microsoft's
755 Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode.
757 - A symbolic link to libcrypto is now added in the kernel sources
758 during kernel compilation
760 - Fixed a couple of 64 bit issues (mostly casts to int).
761 Thanks to Ken Bantoft who checked my sources on a 64 bit platform.
763 - Replaced s[n]printf() statements in the kernel by ipsec_snprintf().
764 Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro
765 of the FreeS/WAN team who solved this problem with the 2.4.25 kernel.
771 - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName
772 certificate extension which contains no generalName item) can cause
773 a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has
774 been hardened to make it more robust against malformed ASN.1 objects.
776 - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native
777 Linux 2.6 IPsec stack.
783 - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12
projects / strongswan.git / blob