4 - New SWIMA IMC/IMV pair implements the "draft-ietf-sacm-nea-swima-patnc"
5 Internet Draft and will be demonstrated at the IETF 99 Prague Hackathon.
7 - The IMV database template has been adapted to achieve full compliancei
8 with the ISO 19770-2:2015 SWID tag standard.
10 - The sw-collector tool extracts software events from apt history logs
11 and stores them in an SQLite database to be used by the SWIMA IMC.
13 - The pt-tls-client can attach and use TPM 2.0 protected private keys
14 via the --keyid parameter.
16 - libtpmtss supports Intel's TSS2 Architecture Broker and Resource
17 Manager interface (tcti-tabrmd).
23 - Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
24 input validation when verifying RSA signatures. More specifically,
25 mpz_powm_sec() has two requirements regarding the passed exponent and modulus
26 that the plugin did not enforce, if these are not met the calculation will
27 result in a floating point exception that crashes the whole process.
28 This vulnerability has been registered as CVE-2017-9022.
30 - Fixed a DoS vulnerability in the x509 plugin that was caused because the ASN.1
31 parser didn't handle ASN.1 CHOICE types properly, which could result in an
32 infinite loop when parsing X.509 extensions that use such types.
33 This vulnerability has been registered as CVE-2017-9023.
35 - The behavior during IKEv2 CHILD_SA rekeying has been changed in order to avoid
36 traffic loss. The responder now only installs the new inbound SA and delays
37 installing the outbound SA until it receives the DELETE for the replaced
38 CHILD_SA. Similarly, the inbound SA of the replaced CHILD_SA is not removed
39 for a configurable amount of seconds (charon.delete_rekeyed_delay) after the
40 DELETE has been processed to reduce the chance of dropping delayed packets.
42 - The code base has been ported to Apple's ARM64 iOS platform, whose calling
43 conventions for variadic and regular functions are different. This means
44 assigning non-variadic functions to variadic function pointers does not work.
45 To avoid this issue the enumerator_t interface has been changed and the
46 signatures of the callback functions for enumerator_create_filter(), and the
47 invoke_function() and find_first() methods on linked_list_t have been changed.
48 The return type of find_first() also changed from status_t to bool.
50 - Added support for fuzzing the certificate parser provided by the default
51 plugins (x509, pem, gmp etc.) on Google's OSS-Fuzz infrastructure. Several
52 issues found while fuzzing these plugins were fixed.
54 - Two new options have been added to charon's retransmission settings:
55 retransmit_limit and retransmit_jitter. The former adds an upper limit to the
56 calculated retransmission timeout, the latter randomly reduces it.
58 - A bug in swanctl's --load-creds command was fixed that caused unencrypted
59 private keys to get unloaded if the command was called multiple times. The
60 load-key VICI command now returns the key ID of the loaded key on success.
62 - The credential manager now enumerates local credential sets before global
63 ones. This means certificates supplied by the peer will now be preferred over
64 certificates with the same identity that may be locally stored (e.g. in the
67 - Added support for hardware offload of IPsec SAs as introduced by Linux 4.11
68 for hardware that supports this.
70 - When building the libraries monolithically and statically the plugin
71 constructors are now hard-coded in each library so the plugin code is not
72 removed by the linker because it thinks none of their symbols are ever
75 - The pki tool loads the curve25519 plugin by default.
81 - Support of Diffie-Hellman group 31 using Curve25519 for IKE as defined
84 - Support of Ed25519 digital signature algorithm for IKEv2 as defined by
85 draft-ietf-ipsecme-eddsa. Ed25519-based public key pairs, X.509 certificates
86 and CRLs can be generated and printed by the pki tool.
88 - The new "tpm" libtpmtss plugin allows to use persistent private RSA and ECDSA
89 keys bound to a TPM 2.0 for both IKE and TLS authentication. Using the
90 TPM 2.0 object handle as keyid parameter, the pki --pub tool can extract
91 the public key from the TPM thereby replacing the aikpub2 tool. In a similar
92 fashion pki --req can generate a PKCS#10 certificate request signed with
95 - The pki tool gained support for generating certificates with the RFC 3779
96 addrblock extension. The charon addrblock plugin now dynamically narrows
97 traffic selectors based on the certificate addrblocks instead of rejecting
98 non-matching selectors completely. This allows generic connections, where
99 the allowed selectors are defined by the used certificates only.
101 - In-place update of cached base and delta CRLs does not leave dozens
102 of stale copies in cache memory.
104 - Several new features for the VICI interface and the swanctl utility: Querying
105 specific pools, enumerating and unloading keys and shared secrets, loading
106 keys and certificates from PKCS#11 tokens, the ability to initiate, install
107 and uninstall connections and policies by their exact name (if multiple child
108 sections in different connections share the same name), a command to initiate
109 the rekeying of IKE and IPsec SAs, support for settings previously only
110 supported by the old config files (plain pubkeys, dscp, certificate policies,
111 IPv6 Transport Proxy Mode, NT Hash secrets, mediation extension).
113 Important: Due to issues with VICI bindings that map sub-sections to
114 dictionaries the CHILD_SA sections returned via list-sas now have a unique
115 name, the original name of a CHILD_SA is returned in the "name" key of its
122 - The newhope plugin implements the post-quantum NewHope key exchange algorithm
123 proposed in their 2015 paper by Erdem Alkim, Léo Ducas, Thomas Pöppelmann and
126 - The libstrongswan crypto factory now offers the registration of Extended
127 Output Functions (XOFs). Currently supported XOFs are SHAKE128 and SHAKE256
128 implemented by the sha3 plugin, ChaCHa20 implemented by the chapoly plugin
129 and the more traditional MGF1 Mask Generation Functions based on the SHA-1,
130 SHA-256 and SHA-512 hash algorithms implemented by the new mgf1 plugin.
132 - The pki tool, with help of the pkcs1 or openssl plugins, can parse private
133 keys in any of the supported formats without having to know the exact type.
134 So instead of having to specify rsa or ecdsa explicitly the keyword priv may
135 be used to indicate a private key of any type. Similarly, swanctl can load
136 any type of private key from the swanctl/private directory.
138 - The pki tool can handle RSASSA-PKCS1v1.5-with-SHA-3 signatures using the
139 sha3 and gmp plugins.
141 - The VICI flush-certs command flushes certificates from the volatile
142 certificate cache. Optionally the type of the certificates to be
143 flushed (e.g. type = x509_crl) can be specified.
145 - Setting cache_crls = yes in strongswan.conf the vici plugin saves regular,
146 base and delta CRLs to disk.
148 - IKE fragmentation is now enabled by default with the default fragment size
149 set to 1280 bytes for both IP address families.
151 - libtpmtss: In the TSS2 API the function TeardownSocketTcti() was replaced by
152 tss2_tcti_finalize().
158 - The new libtpmtss library offers support for both TPM 1.2 and TPM 2.0
159 Trusted Platform Modules. This allows the Attestation IMC/IMV pair to
160 do TPM 2.0 based attestation.
162 - The behavior during IKEv2 exchange collisions has been improved/fixed in
163 several corner cases and support for TEMPORARY_FAILURE and CHILD_SA_NOT_FOUND
164 notifies, as defined by RFC 7296, has been added.
166 - IPsec policy priorities can be set manually (e.g. for high-priority drop
167 policies) and outbound policies may be restricted to a network interface.
169 - The scheme for the automatically calculated default priorities has been
170 changed and now also considers port masks, which were added with 5.4.0.
172 - FWD policies are now installed in both directions in regards to the traffic
173 selectors. Because such "outbound" FWD policies could conflict with "inbound"
174 FWD policies of other SAs they are installed with a lower priority and don't
175 have a reqid set, which allows kernel plugins to distinguish between the two
176 and prefer those with a reqid.
178 - For outbound IPsec SAs no replay window is configured anymore.
180 - Enhanced the functionality of the swanctl --list-conns command by listing
181 IKE_SA and CHILD_SA reauthentication and rekeying settings, and EAP/XAuth
182 identities and EAP types.
184 - DNS servers installed by the resolve plugin are now refcounted, which should
185 fix its use with make-before-break reauthentication. Any output written to
186 stderr/stdout by resolvconf is now logged.
188 - The methods in the kernel interfaces have been changed to take structs instead
189 of long lists of arguments. Similarly the constructors for peer_cfg_t and
190 child_cfg_t now take structs.
196 - Support for IKEv2 redirection (RFC 5685) has been added. Plugins may
197 implement the redirect_provider_t interface to decide if and when to redirect
198 connecting clients. It is also possible to redirect established IKE_SAs based
199 on different selectors via VICI/swanctl. Unless disabled in strongswan.conf
200 the charon daemon will follow redirect requests received from servers.
202 - The ike: prefix enables the explicit configuration of signature scheme
203 constraints against IKEv2 authentication in rightauth, which allows the use
204 of different signature schemes for trustchain verification and authentication.
206 - The initiator of an IKEv2 make-before-break reauthentication now suspends
207 online certificate revocation checks (OCSP, CRLs) until the new IKE_SA and all
208 CHILD_SAs are established. This is required if the checks are done over the
209 CHILD_SA established with the new IKE_SA. This is not possible until the
210 initiator installs this SA and that only happens after the authentication is
211 completed successfully. So we suspend the checks during the reauthentication
212 and do them afterwards, if they fail the IKE_SA is closed. This change has no
213 effect on the behavior during the authentication of the initial IKE_SA.
215 - For the vici plugin a Vici:Session Perl CPAN module has been added to allow
216 Perl applications to control and/or monitor the IKE daemon using the VICI
217 interface, similar to the existing Python egg or Ruby gem.
219 - Traffic selectors with port ranges can now be configured in the Linux kernel:
220 e.g. remote_ts = 10.1.0.0/16[tcp/20-23] local_ts = dynamic[tcp/32768-65535].
221 The port range must map to a port mask, though since the kernel does not
222 support arbitrary ranges.
224 - The vici plugin allows the configuration of IPv4 and IPv6 address ranges
225 in local and remote traffic selectors. Since both the Linux kernel and
226 iptables cannot handle arbitrary ranges, address ranges are mapped to the next
227 larger CIDR subnet by the kernel-netlink and updown plugins, respectively.
229 - Implemented IKEv1 IPv4/IPv6 address subnet and range identities that can be
230 used as owners of shared secrets.
236 - Properly handle potential EINTR errors in sigwaitinfo(2) calls that replaced
237 sigwait(3) calls with 5.3.4.
239 - RADIUS retransmission timeouts are now configurable, courtesy of Thom Troy.
245 - Fixed an authentication bypass vulnerability in the eap-mschapv2 plugin that
246 was caused by insufficient verification of the internal state when handling
247 MSCHAPv2 Success messages received by the client.
248 This vulnerability has been registered as CVE-2015-8023.
250 - The sha3 plugin implements the SHA3 Keccak-F1600 hash algorithm family.
251 Within the strongSwan framework SHA3 is currently used for BLISS signatures
252 only because the OIDs for other signature algorithms haven't been defined
253 yet. Also the use of SHA3 for IKEv2 has not been standardized yet.
259 - Added support for the ChaCha20/Poly1305 AEAD cipher specified in RFC 7539 and
260 RFC 7634 using the chacha20poly1305 ike/esp proposal keyword. The new chapoly
261 plugin implements the cipher, if possible SSE-accelerated on x86/x64
262 architectures. It is usable both in IKEv2 and the strongSwan libipsec ESP
263 backend. On Linux 4.2 or newer the kernel-netlink plugin can configure the
266 - The vici interface now supports the configuration of auxiliary certification
267 authority information as CRL and OCSP URIs.
269 - In the bliss plugin the c_indices derivation using a SHA-512 based random
270 oracle has been fixed, generalized and standardized by employing the MGF1 mask
271 generation function with SHA-512. As a consequence BLISS signatures unsing the
272 improved oracle are not compatible with the earlier implementation.
274 - Support for auto=route with right=%any for transport mode connections has
275 been added (the ikev2/trap-any scenario provides examples).
277 - The starter daemon does not flush IPsec policies and SAs anymore when it is
278 stopped. Already existing duplicate policies are now overwritten by the IKE
279 daemon when it installs its policies.
281 - Init limits (like charon.init_limit_half_open) can now optionally be enforced
282 when initiating SAs via VICI. For this, IKE_SAs initiated by the daemon are
283 now also counted as half-open SAs, which, as a side-effect, fixes the status
284 output while connecting (e.g. in ipsec status).
286 - Symmetric configuration of EAP methods in left|rightauth is now possible when
287 mutual EAP-only authentication is used (previously, the client had to
288 configure rightauth=eap or rightauth=any, which prevented it from using this
289 same config as responder).
291 - The initiator flag in the IKEv2 header is compared again (wasn't the case
292 since 5.0.0) and packets that have the flag set incorrectly are again ignored.
294 - Implemented a demo Hardcopy Device IMC/IMV pair based on the "Hardcopy
295 Device Health Assessment Trusted Network Connect Binding" (HCD-TNC)
296 document drafted by the IEEE Printer Working Group (PWG).
298 - Fixed IF-M segmentation which failed in the presence of multiple small
299 attributes in front of a huge attribute to be segmented.
305 - Fixed a vulnerability that allowed rogue servers with a valid certificate
306 accepted by the client to trick it into disclosing its username and even
307 password (if the client accepts EAP-GTC). This was caused because constraints
308 against the responder's authentication were enforced too late.
309 This vulnerability has been registered as CVE-2015-4171.
315 - Fixed a denial-of-service and potential remote code execution vulnerability
316 triggered by IKEv1/IKEv2 messages that contain payloads for the respective
317 other IKE version. Such payload are treated specially since 5.2.2 but because
318 they were still identified by their original payload type they were used as
319 such in some places causing invalid function pointer dereferences.
320 The vulnerability has been registered as CVE-2015-3991.
322 - The new aesni plugin provides CBC, CTR, XCBC, CMAC, CCM and GCM crypto
323 primitives for AES-128/192/256. The plugin requires AES-NI and PCLMULQDQ
324 instructions and works on both x86 and x64 architectures. It provides
325 superior crypto performance in userland without any external libraries.
331 - Added support for IKEv2 make-before-break reauthentication. By using a global
332 CHILD_SA reqid allocation mechanism, charon supports overlapping CHILD_SAs.
333 This allows the use of make-before-break instead of the previously supported
334 break-before-make reauthentication, avoiding connectivity gaps during that
335 procedure. As the new mechanism may fail with peers not supporting it (such
336 as any previous strongSwan release) it must be explicitly enabled using
337 the charon.make_before_break strongswan.conf option.
339 - Support for "Signature Authentication in IKEv2" (RFC 7427) has been added.
340 This allows the use of stronger hash algorithms for public key authentication.
341 By default, signature schemes are chosen based on the strength of the
342 signature key, but specific hash algorithms may be configured in leftauth.
344 - Key types and hash algorithms specified in rightauth are now also checked
345 against IKEv2 signature schemes. If such constraints are used for certificate
346 chain validation in existing configurations, in particular with peers that
347 don't support RFC 7427, it may be necessary to disable this feature with the
348 charon.signature_authentication_constraints setting, because the signature
349 scheme used in classic IKEv2 public key authentication may not be strong
352 - The new connmark plugin allows a host to bind conntrack flows to a specific
353 CHILD_SA by applying and restoring the SA mark to conntrack entries. This
354 allows a peer to handle multiple transport mode connections coming over the
355 same NAT device for client-initiated flows. A common use case is to protect
356 L2TP/IPsec, as supported by some systems.
358 - The forecast plugin can forward broadcast and multicast messages between
359 connected clients and a LAN. For CHILD_SA using unique marks, it sets up
360 the required Netfilter rules and uses a multicast/broadcast listener that
361 forwards such messages to all connected clients. This plugin is designed for
362 Windows 7 IKEv2 clients, which announces its services over the tunnel if the
363 negotiated IPsec policy allows it.
365 - For the vici plugin a Python Egg has been added to allow Python applications
366 to control or monitor the IKE daemon using the VICI interface, similar to the
367 existing ruby gem. The Python library has been contributed by Björn Schuberg.
369 - EAP server methods now can fulfill public key constraints, such as rightcert
370 or rightca. Additionally, public key and signature constraints can be
371 specified for EAP methods in the rightauth keyword. Currently the EAP-TLS and
372 EAP-TTLS methods provide verification details to constraints checking.
374 - Upgrade of the BLISS post-quantum signature algorithm to the improved BLISS-B
375 variant. Can be used in conjunction with the SHA256, SHA384 and SHA512 hash
376 algorithms with SHA512 being the default.
378 - The IF-IMV 1.4 interface now makes the IP address of the TNC access requestor
379 as seen by the TNC server available to all IMVs. This information can be
380 forwarded to policy enforcement points (e.g. firewalls or routers).
382 - The new mutual tnccs-20 plugin parameter activates mutual TNC measurements
383 in PB-TNC half-duplex mode between two endpoints over either a PT-EAP or
384 PT-TLS transport medium.
390 - Fixed a denial-of-service vulnerability triggered by an IKEv2 Key Exchange
391 payload that contains the Diffie-Hellman group 1025. This identifier was
392 used internally for DH groups with custom generator and prime. Because
393 these arguments are missing when creating DH objects based on the KE payload
394 an invalid pointer dereference occurred. This allowed an attacker to crash
395 the IKE daemon with a single IKE_SA_INIT message containing such a KE
396 payload. The vulnerability has been registered as CVE-2014-9221.
398 - The left/rightid options in ipsec.conf, or any other identity in strongSwan,
399 now accept prefixes to enforce an explicit type, such as email: or fqdn:.
400 Note that no conversion is done for the remaining string, refer to
401 ipsec.conf(5) for details.
403 - The post-quantum Bimodal Lattice Signature Scheme (BLISS) can be used as
404 an IKEv2 public key authentication method. The pki tool offers full support
405 for the generation of BLISS key pairs and certificates.
407 - Fixed mapping of integrity algorithms negotiated for AH via IKEv1. This could
408 cause interoperability issues when connecting to older versions of charon.
414 - The new charon-systemd IKE daemon implements an IKE daemon tailored for use
415 with systemd. It avoids the dependency on ipsec starter and uses swanctl
416 as configuration backend, building a simple and lightweight solution. It
417 supports native systemd journal logging.
419 - Support for IKEv2 fragmentation as per RFC 7383 has been added. Like IKEv1
420 fragmentation it can be enabled by setting fragmentation=yes in ipsec.conf.
422 - Support of the TCG TNC IF-M Attribute Segmentation specification proposal.
423 All attributes can be segmented. Additionally TCG/SWID Tag, TCG/SWID Tag ID
424 and IETF/Installed Packages attributes can be processed incrementally on a
427 - The new ext-auth plugin calls an external script to implement custom IKE_SA
428 authorization logic, courtesy of Vyronas Tsingaras.
430 - For the vici plugin a ruby gem has been added to allow ruby applications
431 to control or monitor the IKE daemon. The vici documentation has been updated
432 to include a description of the available operations and some simple examples
433 using both the libvici C interface and the ruby gem.
439 - strongSwan has been ported to the Windows platform. Using a MinGW toolchain,
440 many parts of the strongSwan codebase run natively on Windows 7 / 2008 R2
441 and newer releases. charon-svc implements a Windows IKE service based on
442 libcharon, the kernel-iph and kernel-wfp plugins act as networking and IPsec
443 backend on the Windows platform. socket-win provides a native IKE socket
444 implementation, while winhttp fetches CRL and OCSP information using the
447 - The new vici plugin provides a Versatile IKE Configuration Interface for
448 charon. Using the stable IPC interface, external applications can configure,
449 control and monitor the IKE daemon. Instead of scripting the ipsec tool
450 and generating ipsec.conf, third party applications can use the new interface
451 for more control and better reliability.
453 - Built upon the libvici client library, swanctl implements the first user of
454 the VICI interface. Together with a swanctl.conf configuration file,
455 connections can be defined, loaded and managed. swanctl provides a portable,
456 complete IKE configuration and control interface for the command line.
457 The first six swanctl example scenarios have been added.
459 - The SWID IMV implements a JSON-based REST API which allows the exchange
460 of SWID tags and Software IDs with the strongTNC policy manager.
462 - The SWID IMC can extract all installed packages from the dpkg (Debian,
463 Ubuntu, Linux Mint etc.), rpm (Fedora, RedHat, OpenSUSE, etc.), or
464 pacman (Arch Linux, Manjaro, etc.) package managers, respectively, using the
465 swidGenerator (https://github.com/strongswan/swidGenerator) which generates
466 SWID tags according to the new ISO/IEC 19770-2:2014 standard.
468 - All IMVs now share the access requestor ID, device ID and product info
469 of an access requestor via a common imv_session object.
471 - The Attestation IMC/IMV pair supports the IMA-NG measurement format
472 introduced with the Linux 3.13 kernel.
474 - The aikgen tool generates an Attestation Identity Key bound to a TPM.
476 - Implemented the PT-EAP transport protocol (RFC 7171) for Trusted Network
479 - The ipsec.conf replay_window option defines connection specific IPsec replay
480 windows. Original patch courtesy of Zheng Zhong and Christophe Gouault from
487 - Fixed an authentication bypass vulnerability triggered by rekeying an
488 unestablished IKEv2 SA while it gets actively initiated. This allowed an
489 attacker to trick a peer's IKE_SA state to established, without the need to
490 provide any valid authentication credentials. The vulnerability has been
491 registered as CVE-2014-2338.
493 - The acert plugin evaluates X.509 Attribute Certificates. Group membership
494 information encoded as strings can be used to fulfill authorization checks
495 defined with the rightgroups option. Attribute Certificates can be loaded
496 locally or get exchanged in IKEv2 certificate payloads.
498 - The pki command gained support to generate X.509 Attribute Certificates
499 using the --acert subcommand, while the --print command supports the ac type.
500 The openac utility has been removed in favor of the new pki functionality.
502 - The libtls TLS 1.2 implementation as used by EAP-(T)TLS and other protocols
503 has been extended by AEAD mode support, currently limited to AES-GCM.
509 - A new default configuration file layout is introduced. The new default
510 strongswan.conf file mainly includes config snippets from the strongswan.d
511 and strongswan.d/charon directories (the latter containing snippets for all
512 plugins). The snippets, with commented defaults, are automatically
513 generated and installed, if they don't exist yet. They are also installed
514 in $prefix/share/strongswan/templates so existing files can be compared to
515 the current defaults.
517 - As an alternative to the non-extensible charon.load setting, the plugins
518 to load in charon (and optionally other applications) can now be determined
519 via the charon.plugins.<name>.load setting for each plugin (enabled in the
520 new default strongswan.conf file via the charon.load_modular option).
521 The load setting optionally takes a numeric priority value that allows
522 reordering the plugins (otherwise the default plugin order is preserved).
524 - All strongswan.conf settings that were formerly defined in library specific
525 "global" sections are now application specific (e.g. settings for plugins in
526 libstrongswan.plugins can now be set only for charon in charon.plugins).
527 The old options are still supported, which now allows to define defaults for
528 all applications in the libstrongswan section.
530 - The ntru libstrongswan plugin supports NTRUEncrypt as a post-quantum
531 computer IKE key exchange mechanism. The implementation is based on the
532 ntru-crypto library from the NTRUOpenSourceProject. The supported security
533 strengths are ntru112, ntru128, ntru192, and ntru256. Since the private DH
534 group IDs 1030..1033 have been assigned, the strongSwan Vendor ID must be
535 sent (charon.send_vendor_id = yes) in order to use NTRU.
537 - Defined a TPMRA remote attestation workitem and added support for it to the
540 - Compatibility issues between IPComp (compress=yes) and leftfirewall=yes as
541 well as multiple subnets in left|rightsubnet have been fixed.
543 - When enabling its "session" strongswan.conf option, the xauth-pam plugin opens
544 and closes a PAM session for each established IKE_SA. Patch courtesy of
547 - The strongSwan unit testing framework has been rewritten without the "check"
548 dependency for improved flexibility and portability. It now properly supports
549 multi-threaded and memory leak testing and brings a bunch of new test cases.
555 - Fixed a denial-of-service vulnerability and potential authorization bypass
556 triggered by a crafted ID_DER_ASN1_DN ID payload. The cause is an insufficient
557 length check when comparing such identities. The vulnerability has been
558 registered as CVE-2013-6075.
560 - Fixed a denial-of-service vulnerability triggered by a crafted IKEv1
561 fragmentation payload. The cause is a NULL pointer dereference. The
562 vulnerability has been registered as CVE-2013-6076.
564 - The lean stand-alone pt-tls-client can set up a RFC 6876 PT-TLS session
565 with a strongSwan policy enforcement point which uses the tnc-pdp charon
568 - The new TCG TNC SWID IMC/IMV pair supports targeted SWID requests for either
569 full SWID Tag or concise SWID Tag ID inventories.
571 - The XAuth backend in eap-radius now supports multiple XAuth exchanges for
572 different credential types and display messages. All user input gets
573 concatenated and verified with a single User-Password RADIUS attribute on
574 the AAA. With an AAA supporting it, one for example can implement
575 Password+Token authentication with proper dialogs on iOS and OS X clients.
577 - charon supports IKEv1 Mode Config exchange in push mode. The ipsec.conf
578 modeconfig=push option enables it for both client and server, the same way
581 - Using the "ah" ipsec.conf keyword on both IKEv1 and IKEv2 connections,
582 charon can negotiate and install Security Associations integrity-protected by
583 the Authentication Header protocol. Supported are plain AH(+IPComp) SAs only,
584 but not the deprecated RFC2401 style ESP+AH bundles.
586 - The generation of initialization vectors for IKE and ESP (when using libipsec)
587 is now modularized and IVs for e.g. AES-GCM are now correctly allocated
588 sequentially, while other algorithms like AES-CBC still use random IVs.
590 - The left and right options in ipsec.conf can take multiple address ranges
591 and subnets. This allows connection matching against a larger set of
592 addresses, for example to use a different connection for clients connecting
593 from a internal network.
595 - For all those who have a queasy feeling about the NIST elliptic curve set,
596 the Brainpool curves introduced for use with IKE by RFC 6932 might be a
597 more trustworthy alternative.
599 - The kernel-libipsec userland IPsec backend now supports usage statistics,
600 volume based rekeying and accepts ESPv3 style TFC padded packets.
602 - With two new strongswan.conf options fwmarks can be used to implement
603 host-to-host tunnels with kernel-libipsec.
605 - load-tester supports transport mode connections and more complex traffic
606 selectors, including such using unique ports for each tunnel.
608 - The new dnscert plugin provides support for authentication via CERT RRs that
609 are protected via DNSSEC. The plugin was created by Ruslan N. Marchenko.
611 - The eap-radius plugin supports forwarding of several Cisco Unity specific
612 RADIUS attributes in corresponding configuration payloads.
614 - Database transactions are now abstracted and implemented by the two backends.
615 If you use MySQL make sure all tables use the InnoDB engine.
617 - libstrongswan now can provide an experimental custom implementation of the
618 printf family functions based on klibc if neither Vstr nor glibc style printf
619 hooks are available. This can avoid the Vstr dependency on some systems at
620 the cost of slower and less complete printf functions.
626 - Fixed a denial-of-service vulnerability triggered by specific XAuth usernames
627 and EAP identities (since 5.0.3), and PEM files (since 4.1.11). The crash
628 was caused by insufficient error handling in the is_asn1() function.
629 The vulnerability has been registered as CVE-2013-5018.
631 - The new charon-cmd command line IKE client can establish road warrior
632 connections using IKEv1 or IKEv2 with different authentication profiles.
633 It does not depend on any configuration files and can be configured using a
634 few simple command line options.
636 - The kernel-pfroute networking backend has been greatly improved. It now
637 can install virtual IPs on TUN devices on OS X and FreeBSD, allowing these
638 systems to act as a client in common road warrior scenarios.
640 - The new kernel-libipsec plugin uses TUN devices and libipsec to provide IPsec
641 processing in userland on Linux, FreeBSD and Mac OS X.
643 - The eap-radius plugin can now serve as an XAuth backend called xauth-radius,
644 directly verifying XAuth credentials using RADIUS User-Name/User-Password
645 attributes. This is more efficient than the existing xauth-eap+eap-radius
646 combination, and allows RADIUS servers without EAP support to act as AAA
649 - The new osx-attr plugin installs configuration attributes (currently DNS
650 servers) via SystemConfiguration on Mac OS X. The keychain plugin provides
651 certificates from the OS X keychain service.
653 - The sshkey plugin parses SSH public keys, which, together with the --agent
654 option for charon-cmd, allows the use of ssh-agent for authentication.
655 To configure SSH keys in ipsec.conf the left|rightrsasigkey options are
656 replaced with left|rightsigkey, which now take public keys in one of three
657 formats: SSH (RFC 4253, ssh: prefix), DNSKEY (RFC 3110, dns: prefix), and
658 PKCS#1 (the default, no prefix).
660 - Extraction of certificates and private keys from PKCS#12 files is now provided
661 by the new pkcs12 plugin or the openssl plugin. charon-cmd (--p12) as well
662 as charon (via P12 token in ipsec.secrets) can make use of this.
664 - IKEv2 can now negotiate transport mode and IPComp in NAT situations.
666 - IKEv2 exchange initiators now properly close an established IKE or CHILD_SA
667 on error conditions using an additional exchange, keeping state in sync
670 - Using a SQL database interface a Trusted Network Connect (TNC) Policy Manager
671 can generate specific measurement workitems for an arbitrary number of
672 Integrity Measurement Verifiers (IMVs) based on the history of the VPN user
675 - Several core classes in libstrongswan are now tested with unit tests. These
676 can be enabled with --enable-unit-tests and run with 'make check'. Coverage
677 reports can be generated with --enable-coverage and 'make coverage' (this
678 disables any optimization, so it should not be enabled when building
679 production releases).
681 - The leak-detective developer tool has been greatly improved. It works much
682 faster/stabler with multiple threads, does not use deprecated malloc hooks
683 anymore and has been ported to OS X.
685 - chunk_hash() is now based on SipHash-2-4 with a random key. This provides
686 better distribution and prevents hash flooding attacks when used with
689 - All default plugins implement the get_features() method to define features
690 and their dependencies. The plugin loader has been improved, so that plugins
691 in a custom load statement can be ordered freely or to express preferences
692 without being affected by dependencies between plugin features.
694 - A centralized thread can take care for watching multiple file descriptors
695 concurrently. This removes the need for a dedicated listener threads in
696 various plugins. The number of "reserved" threads for such tasks has been
697 reduced to about five, depending on the plugin configuration.
699 - Plugins that can be controlled by a UNIX socket IPC mechanism gained network
700 transparency. Third party applications querying these plugins now can use
701 TCP connections from a different host.
703 - libipsec now supports AES-GCM.
709 - Fixed a security vulnerability in the openssl plugin which was reported by
710 Kevin Wojtysiak. The vulnerability has been registered as CVE-2013-2944.
711 Before the fix, if the openssl plugin's ECDSA signature verification was used,
712 due to a misinterpretation of the error code returned by the OpenSSL
713 ECDSA_verify() function, an empty or zeroed signature was accepted as a
716 - The handling of a couple of other non-security relevant openssl return codes
719 - The tnc_ifmap plugin now publishes virtual IPv4 and IPv6 addresses via its
720 TCG TNC IF-MAP 2.1 interface.
722 - The charon.initiator_only option causes charon to ignore IKE initiation
725 - The openssl plugin can now use the openssl-fips library.
731 - The new ipseckey plugin enables authentication based on trustworthy public
732 keys stored as IPSECKEY resource records in the DNS and protected by DNSSEC.
733 To do so it uses a DNSSEC enabled resolver, like the one provided by the new
734 unbound plugin, which is based on libldns and libunbound. Both plugins were
735 created by Reto Guadagnini.
737 - Implemented the TCG TNC IF-IMV 1.4 draft making access requestor identities
738 available to an IMV. The OS IMV stores the AR identity together with the
739 device ID in the attest database.
741 - The openssl plugin now uses the AES-NI accelerated version of AES-GCM
742 if the hardware supports it.
744 - The eap-radius plugin can now assign virtual IPs to IKE clients using the
745 Framed-IP-Address attribute by using the "%radius" named pool in the
746 rightsourceip ipsec.conf option. Cisco Banner attributes are forwarded to
747 Unity-capable IKEv1 clients during mode config. charon now sends Interim
748 Accounting updates if requested by the RADIUS server, reports
749 sent/received packets in Accounting messages, and adds a Terminate-Cause
752 - The recently introduced "ipsec listcounters" command can report connection
753 specific counters by passing a connection name, and global or connection
754 counters can be reset by the "ipsec resetcounters" command.
756 - The strongSwan libpttls library provides an experimental implementation of
757 PT-TLS (RFC 6876), a Posture Transport Protocol over TLS.
759 - The charon systime-fix plugin can disable certificate lifetime checks on
760 embedded systems if the system time is obviously out of sync after bootup.
761 Certificates lifetimes get checked once the system time gets sane, closing
762 or reauthenticating connections using expired certificates.
764 - The "ikedscp" ipsec.conf option can set DiffServ code points on outgoing
767 - The new xauth-noauth plugin allows to use basic RSA or PSK authentication with
768 clients that cannot be configured without XAuth authentication. The plugin
769 simply concludes the XAuth exchange successfully without actually performing
770 any authentication. Therefore, to use this backend it has to be selected
771 explicitly with rightauth2=xauth-noauth.
773 - The new charon-tkm IKEv2 daemon delegates security critical operations to a
774 separate process. This has the benefit that the network facing daemon has no
775 knowledge of keying material used to protect child SAs. Thus subverting
776 charon-tkm does not result in the compromise of cryptographic keys.
777 The extracted functionality has been implemented from scratch in a minimal TCB
778 (trusted computing base) in the Ada programming language. Further information
779 can be found at http://www.codelabs.ch/tkm/.
784 - Implemented all IETF Standard PA-TNC attributes and an OS IMC/IMV
785 pair using them to transfer operating system information.
787 - The new "ipsec listcounters" command prints a list of global counter values
788 about received and sent IKE messages and rekeyings.
790 - A new lookip plugin can perform fast lookup of tunnel information using a
791 clients virtual IP and can send notifications about established or deleted
792 tunnels. The "ipsec lookip" command can be used to query such information
793 or receive notifications.
795 - The new error-notify plugin catches some common error conditions and allows
796 an external application to receive notifications for them over a UNIX socket.
798 - IKE proposals can now use a PRF algorithm different to that defined for
799 integrity protection. If an algorithm with a "prf" prefix is defined
800 explicitly (such as prfsha1 or prfsha256), no implicit PRF algorithm based on
801 the integrity algorithm is added to the proposal.
803 - The pkcs11 plugin can now load leftcert certificates from a smartcard for a
804 specific ipsec.conf conn section and cacert CA certificates for a specific ca
807 - The load-tester plugin gained additional options for certificate generation
808 and can load keys and multiple CA certificates from external files. It can
809 install a dedicated outer IP address for each tunnel and tunnel initiation
810 batches can be triggered and monitored externally using the
811 "ipsec load-tester" tool.
813 - PKCS#7 container parsing has been modularized, and the openssl plugin
814 gained an alternative implementation to decrypt and verify such files.
815 In contrast to our own DER parser, OpenSSL can handle BER files, which is
816 required for interoperability of our scepclient with EJBCA.
818 - Support for the proprietary IKEv1 fragmentation extension has been added.
819 Fragments are always handled on receipt but only sent if supported by the peer
820 and if enabled with the new fragmentation ipsec.conf option.
822 - IKEv1 in charon can now parse certificates received in PKCS#7 containers and
823 supports NAT traversal as used by Windows clients. Patches courtesy of
826 - The new rdrand plugin provides a high quality / high performance random
827 source using the Intel rdrand instruction found on Ivy Bridge processors.
829 - The integration test environment was updated and now uses KVM and reproducible
830 guest images based on Debian.
836 - Introduced the sending of the standard IETF Assessment Result
837 PA-TNC attribute by all strongSwan Integrity Measurement Verifiers.
839 - Extended PTS Attestation IMC/IMV pair to provide full evidence of
840 the Linux IMA measurement process. All pertinent file information
841 of a Linux OS can be collected and stored in an SQL database.
843 - The PA-TNC and PB-TNC protocols can now process huge data payloads
844 >64 kB by distributing PA-TNC attributes over multiple PA-TNC messages
845 and these messages over several PB-TNC batches. As long as no
846 consolidated recommandation from all IMVs can be obtained, the TNC
847 server requests more client data by sending an empty SDATA batch.
849 - The rightgroups2 ipsec.conf option can require group membership during
850 a second authentication round, for example during XAuth authentication
851 against a RADIUS server.
853 - The xauth-pam backend can authenticate IKEv1 XAuth and Hybrid authenticated
854 clients against any PAM service. The IKEv2 eap-gtc plugin does not use
855 PAM directly anymore, but can use any XAuth backend to verify credentials,
858 - The new unity plugin brings support for some parts of the IKEv1 Cisco Unity
859 Extension. As client, charon narrows traffic selectors to the received
860 Split-Include attributes and automatically installs IPsec bypass policies
861 for received Local-LAN attributes. As server, charon sends Split-Include
862 attributes for leftsubnet definitions containing multiple subnets to Unity-
865 - An EAP-Nak payload is returned by clients if the gateway requests an EAP
866 method that the client does not support. Clients can also request a specific
867 EAP method by configuring that method with leftauth.
869 - The eap-dynamic plugin handles EAP-Nak payloads returned by clients and uses
870 these to select a different EAP method supported/requested by the client.
871 The plugin initially requests the first registered method or the first method
872 configured with charon.plugins.eap-dynamic.preferred.
874 - The new left/rightdns options specify connection specific DNS servers to
875 request/respond in IKEv2 configuration payloads or IKEv2 mode config. leftdns
876 can be any (comma separated) combination of %config4 and %config6 to request
877 multiple servers, both for IPv4 and IPv6. rightdns takes a list of DNS server
878 IP addresses to return.
880 - The left/rightsourceip options now accept multiple addresses or pools.
881 leftsourceip can be any (comma separated) combination of %config4, %config6
882 or fixed IP addresses to request. rightsourceip accepts multiple explicitly
883 specified or referenced named pools.
885 - Multiple connections can now share a single address pool when they use the
886 same definition in one of the rightsourceip pools.
888 - The options charon.interfaces_ignore and charon.interfaces_use allow one to
889 configure the network interfaces used by the daemon.
891 - The kernel-netlink plugin supports the charon.install_virtual_ip_on option,
892 which specifies the interface on which virtual IP addresses will be installed.
893 If it is not specified the current behavior of using the outbound interface
896 - The kernel-netlink plugin tries to keep the current source address when
897 looking for valid routes to reach other hosts.
899 - The autotools build has been migrated to use a config.h header. strongSwan
900 development headers will get installed during "make install" if
901 --with-dev-headers has been passed to ./configure.
903 - All crypto primitives gained return values for most operations, allowing
904 crypto backends to fail, for example when using hardware accelerators.
910 - The charon IKE daemon gained experimental support for the IKEv1 protocol.
911 Pluto has been removed from the 5.x series, and unless strongSwan is
912 configured with --disable-ikev1 or --disable-ikev2, charon handles both
913 keying protocols. The feature-set of IKEv1 in charon is almost on par with
914 pluto, but currently does not support AH or bundled AH+ESP SAs. Beside
915 RSA/ECDSA, PSK and XAuth, charon also supports the Hybrid authentication
916 mode. Informations for interoperability and migration is available at
917 http://wiki.strongswan.org/projects/strongswan/wiki/CharonPlutoIKEv1.
919 - Charon's bus_t has been refactored so that loggers and other listeners are
920 now handled separately. The single lock was previously cause for deadlocks
921 if extensive listeners, such as the one provided by the updown plugin, wanted
922 to acquire locks that were held by other threads which in turn tried to log
923 messages, and thus were waiting to acquire the same lock currently held by
924 the thread calling the listener.
925 The implemented changes also allow the use of a read/write-lock for the
926 loggers which increases performance if multiple loggers are registered.
927 Besides several interface changes this last bit also changes the semantics
928 for loggers as these may now be called by multiple threads at the same time.
930 - Source routes are reinstalled if interfaces are reactivated or IP addresses
933 - The thread pool (processor_t) now has more control over the lifecycle of
934 a job (see job.h for details). In particular, it now controls the destruction
935 of jobs after execution and the cancellation of jobs during shutdown. Due to
936 these changes the requeueing feature, previously available to callback_job_t
937 only, is now available to all jobs (in addition to a new rescheduling
940 - In addition to trustchain key strength definitions for different public key
941 systems, the rightauth option now takes a list of signature hash algorithms
942 considered save for trustchain validation. For example, the setting
943 rightauth=rsa-2048-ecdsa-256-sha256-sha384-sha512 requires a trustchain
944 that uses at least RSA-2048 or ECDSA-256 keys and certificate signatures
945 using SHA-256 or better.
951 - Fixed a security vulnerability in the gmp plugin. If this plugin was used
952 for RSA signature verification an empty or zeroed signature was handled as
955 - Fixed several issues with reauthentication and address updates.
961 - The tnc-pdp plugin implements a RADIUS server interface allowing
962 a strongSwan TNC server to act as a Policy Decision Point.
964 - The eap-radius authentication backend enforces Session-Timeout attributes
965 using RFC4478 repeated authentication and acts upon RADIUS Dynamic
966 Authorization extensions, RFC 5176. Currently supported are disconnect
967 requests and CoA messages containing a Session-Timeout.
969 - The eap-radius plugin can forward arbitrary RADIUS attributes from and to
970 clients using custom IKEv2 notify payloads. The new radattr plugin reads
971 attributes to include from files and prints received attributes to the
974 - Added support for untruncated MD5 and SHA1 HMACs in ESP as used in
977 - The cmac plugin implements the AES-CMAC-96 and AES-CMAC-PRF-128 algorithms
978 as defined in RFC 4494 and RFC 4615, respectively.
980 - The resolve plugin automatically installs nameservers via resolvconf(8),
981 if it is installed, instead of modifying /etc/resolv.conf directly.
983 - The IKEv2 charon daemon supports now raw RSA public keys in RFC 3110
984 DNSKEY and PKCS#1 file format.
990 - Upgraded the TCG IF-IMC and IF-IMV C API to the upcoming version 1.3
991 which supports IF-TNCCS 2.0 long message types, the exclusive flags
992 and multiple IMC/IMV IDs. Both the TNC Client and Server as well as
993 the "Test", "Scanner", and "Attestation" IMC/IMV pairs were updated.
995 - Fully implemented the "TCG Attestation PTS Protocol: Binding to IF-M"
996 standard (TLV-based messages only). TPM-based remote attestation of
997 Linux IMA (Integrity Measurement Architecture) possible. Measurement
998 reference values are automatically stored in an SQLite database.
1000 - The EAP-RADIUS authentication backend supports RADIUS accounting. It sends
1001 start/stop messages containing Username, Framed-IP and Input/Output-Octets
1002 attributes and has been tested against FreeRADIUS and Microsoft NPS.
1004 - Added support for PKCS#8 encoded private keys via the libstrongswan
1005 pkcs8 plugin. This is the default format used by some OpenSSL tools since
1006 version 1.0.0 (e.g. openssl req with -keyout).
1008 - Added session resumption support to the strongSwan TLS stack.
1014 - Because of changing checksums before and after installation which caused
1015 the integrity tests to fail we avoided directly linking libsimaka, libtls and
1016 libtnccs to those libcharon plugins which make use of these dynamic libraries.
1017 Instead we linked the libraries to the charon daemon. Unfortunately Ubuntu
1018 11.10 activated the --as-needed ld option which discards explicit links
1019 to dynamic libraries that are not actually used by the charon daemon itself,
1020 thus causing failures during the loading of the plugins which depend on these
1021 libraries for resolving external symbols.
1023 - Therefore our approach of computing integrity checksums for plugins had to be
1024 changed radically by moving the hash generation from the compilation to the
1025 post-installation phase.
1031 - The new libstrongswan certexpire plugin collects expiration information of
1032 all used certificates and exports them to CSV files. It either directly
1033 exports them or uses cron style scheduling for batch exports.
1035 - starter passes unresolved hostnames to charon, allowing it to do name
1036 resolution not before the connection attempt. This is especially useful with
1037 connections between hosts using dynamic IP addresses. Thanks to Mirko Parthey
1038 for the initial patch.
1040 - The android plugin can now be used without the Android frontend patch and
1041 provides DNS server registration and logging to logcat.
1043 - Pluto and starter (plus stroke and whack) have been ported to Android.
1045 - Support for ECDSA private and public key operations has been added to the
1046 pkcs11 plugin. The plugin now also provides DH and ECDH via PKCS#11 and can
1047 use tokens as random number generators (RNG). By default only private key
1048 operations are enabled, more advanced features have to be enabled by their
1049 option in strongswan.conf. This also applies to public key operations (even
1050 for keys not stored on the token) which were enabled by default before.
1052 - The libstrongswan plugin system now supports detailed plugin dependencies.
1053 Many plugins have been extended to export its capabilities and requirements.
1054 This allows the plugin loader to resolve plugin loading order automatically,
1055 and in future releases, to dynamically load the required features on demand.
1056 Existing third party plugins are source (but not binary) compatible if they
1057 properly initialize the new get_features() plugin function to NULL.
1059 - The tnc-ifmap plugin implements a TNC IF-MAP 2.0 client which can deliver
1060 metadata about IKE_SAs via a SOAP interface to a MAP server. The tnc-ifmap
1061 plugin requires the Apache Axis2/C library.
1067 - Our private libraries (e.g. libstrongswan) are not installed directly in
1068 prefix/lib anymore. Instead a subdirectory is used (prefix/lib/ipsec/ by
1069 default). The plugins directory is also moved from libexec/ipsec/ to that
1072 - The dynamic IMC/IMV libraries were moved from the plugins directory to
1073 a new imcvs directory in the prefix/lib/ipsec/ subdirectory.
1075 - Job priorities were introduced to prevent thread starvation caused by too
1076 many threads handling blocking operations (such as CRL fetching). Refer to
1077 strongswan.conf(5) for details.
1079 - Two new strongswan.conf options allow to fine-tune performance on IKEv2
1080 gateways by dropping IKE_SA_INIT requests on high load.
1082 - IKEv2 charon daemon supports start PASS and DROP shunt policies
1083 preventing traffic to go through IPsec connections. Installation of the
1084 shunt policies either via the XFRM netfilter or PFKEYv2 IPsec kernel
1087 - The history of policies installed in the kernel is now tracked so that e.g.
1088 trap policies are correctly updated when reauthenticated SAs are terminated.
1090 - IMC/IMV Scanner pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1091 Using "netstat -l" the IMC scans open listening ports on the TNC client
1092 and sends a port list to the IMV which based on a port policy decides if
1093 the client is admitted to the network.
1094 (--enable-imc-scanner/--enable-imv-scanner).
1096 - IMC/IMV Test pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1097 (--enable-imc-test/--enable-imv-test).
1099 - The IKEv2 close action does not use the same value as the ipsec.conf dpdaction
1100 setting, but the value defined by its own closeaction keyword. The action
1101 is triggered if the remote peer closes a CHILD_SA unexpectedly.
1107 - The whitelist plugin for the IKEv2 daemon maintains an in-memory identity
1108 whitelist. Any connection attempt of peers not whitelisted will get rejected.
1109 The 'ipsec whitelist' utility provides a simple command line frontend for
1110 whitelist administration.
1112 - The duplicheck plugin provides a specialized form of duplicate checking,
1113 doing a liveness check on the old SA and optionally notify a third party
1114 application about detected duplicates.
1116 - The coupling plugin permanently couples two or more devices by limiting
1117 authentication to previously used certificates.
1119 - In the case that the peer config and child config don't have the same name
1120 (usually in SQL database defined connections), ipsec up|route <peer config>
1121 starts|routes all associated child configs and ipsec up|route <child config>
1122 only starts|routes the specific child config.
1124 - fixed the encoding and parsing of X.509 certificate policy statements (CPS).
1126 - Duncan Salerno contributed the eap-sim-pcsc plugin implementing a
1127 pcsc-lite based SIM card backend.
1129 - The eap-peap plugin implements the EAP PEAP protocol. Interoperates
1130 successfully with a FreeRADIUS server and Windows 7 Agile VPN clients.
1132 - The IKEv2 daemon charon rereads strongswan.conf on SIGHUP and instructs
1133 all plugins to reload. Currently only the eap-radius and the attr plugins
1134 support configuration reloading.
1136 - Added userland support to the IKEv2 daemon for Extended Sequence Numbers
1137 support coming with Linux 2.6.39. To enable ESN on a connection, add
1138 the 'esn' keyword to the proposal. The default proposal uses 32-bit sequence
1139 numbers only ('noesn'), and the same value is used if no ESN mode is
1140 specified. To negotiate ESN support with the peer, include both, e.g.
1141 esp=aes128-sha1-esn-noesn.
1143 - In addition to ESN, Linux 2.6.39 gained support for replay windows larger
1144 than 32 packets. The new global strongswan.conf option 'charon.replay_window'
1145 configures the size of the replay window, in packets.
1151 - Sansar Choinyambuu implemented the RFC 5793 Posture Broker Protocol (BP)
1152 compatible with Trusted Network Connect (TNC). The TNCCS 2.0 protocol
1153 requires the tnccs_20, tnc_imc and tnc_imv plugins but does not depend
1154 on the libtnc library. Any available IMV/IMC pairs conforming to the
1155 Trusted Computing Group's TNC-IF-IMV/IMC 1.2 interface specification
1156 can be loaded via /etc/tnc_config.
1158 - Re-implemented the TNCCS 1.1 protocol by using the tnc_imc and tnc_imv
1159 in place of the external libtnc library.
1161 - The tnccs_dynamic plugin loaded on a TNC server in addition to the
1162 tnccs_11 and tnccs_20 plugins, dynamically detects the IF-TNCCS
1163 protocol version used by a TNC client and invokes an instance of
1164 the corresponding protocol stack.
1166 - IKE and ESP proposals can now be stored in an SQL database using a
1167 new proposals table. The start_action field in the child_configs
1168 tables allows the automatic starting or routing of connections stored
1171 - The new certificate_authorities and certificate_distribution_points
1172 tables make it possible to store CRL and OCSP Certificate Distribution
1173 points in an SQL database.
1175 - The new 'include' statement allows to recursively include other files in
1176 strongswan.conf. Existing sections and values are thereby extended and
1177 replaced, respectively.
1179 - Due to the changes in the parser for strongswan.conf, the configuration
1180 syntax for the attr plugin has changed. Previously, it was possible to
1181 specify multiple values of a specific attribute type by adding multiple
1182 key/value pairs with the same key (e.g. dns) to the plugins.attr section.
1183 Because values with the same key now replace previously defined values
1184 this is not possible anymore. As an alternative, multiple values can be
1185 specified by separating them with a comma (e.g. dns = 1.2.3.4, 2.3.4.5).
1187 - ipsec listalgs now appends (set in square brackets) to each crypto
1188 algorithm listed the plugin that registered the function.
1190 - Traffic Flow Confidentiality padding supported with Linux 2.6.38 can be used
1191 by the IKEv2 daemon. The ipsec.conf 'tfc' keyword pads all packets to a given
1192 boundary, the special value '%mtu' pads all packets to the path MTU.
1194 - The new af-alg plugin can use various crypto primitives of the Linux Crypto
1195 API using the AF_ALG interface introduced with 2.6.38. This removes the need
1196 for additional userland implementations of symmetric cipher, hash, hmac and
1199 - The IKEv2 daemon supports the INITIAL_CONTACT notify as initiator and
1200 responder. The notify is sent when initiating configurations with a unique
1201 policy, set in ipsec.conf via the global 'uniqueids' option.
1203 - The conftest conformance testing framework enables the IKEv2 stack to perform
1204 many tests using a distinct tool and configuration frontend. Various hooks
1205 can alter reserved bits, flags, add custom notifies and proposals, reorder
1206 or drop messages and much more. It is enabled using the --enable-conftest
1209 - The new libstrongswan constraints plugin provides advanced X.509 constraint
1210 checking. In addition to X.509 pathLen constraints, the plugin checks for
1211 nameConstraints and certificatePolicies, including policyMappings and
1212 policyConstraints. The x509 certificate plugin and the pki tool have been
1213 enhanced to support these extensions. The new left/rightcertpolicy ipsec.conf
1214 connection keywords take OIDs a peer certificate must have.
1216 - The left/rightauth ipsec.conf keywords accept values with a minimum strength
1217 for trustchain public keys in bits, such as rsa-2048 or ecdsa-256.
1219 - The revocation and x509 libstrongswan plugins and the pki tool gained basic
1220 support for delta CRLs.
1226 - IMPORTANT: the default keyexchange mode 'ike' is changing with release 4.5
1227 from 'ikev1' to 'ikev2', thus commemorating the five year anniversary of the
1228 IKEv2 RFC 4306 and its mature successor RFC 5996. The time has definitively
1229 come for IKEv1 to go into retirement and to cede its place to the much more
1230 robust, powerful and versatile IKEv2 protocol!
1232 - Added new ctr, ccm and gcm plugins providing Counter, Counter with CBC-MAC
1233 and Galois/Counter Modes based on existing CBC implementations. These
1234 new plugins bring support for AES and Camellia Counter and CCM algorithms
1235 and the AES GCM algorithms for use in IKEv2.
1237 - The new pkcs11 plugin brings full Smartcard support to the IKEv2 daemon and
1238 the pki utility using one or more PKCS#11 libraries. It currently supports
1239 RSA private and public key operations and loads X.509 certificates from
1242 - Implemented a general purpose TLS stack based on crypto and credential
1243 primitives of libstrongswan. libtls supports TLS versions 1.0, 1.1 and 1.2,
1244 ECDHE-ECDSA/RSA, DHE-RSA and RSA key exchange algorithms and RSA/ECDSA based
1245 client authentication.
1247 - Based on libtls, the eap-tls plugin brings certificate based EAP
1248 authentication for client and server. It is compatible to Windows 7 IKEv2
1249 Smartcard authentication and the OpenSSL based FreeRADIUS EAP-TLS backend.
1251 - Implemented the TNCCS 1.1 Trusted Network Connect protocol using the
1252 libtnc library on the strongSwan client and server side via the tnccs_11
1253 plugin and optionally connecting to a TNC@FHH-enhanced FreeRADIUS AAA server.
1254 Depending on the resulting TNC Recommendation, strongSwan clients are granted
1255 access to a network behind a strongSwan gateway (allow), are put into a
1256 remediation zone (isolate) or are blocked (none), respectively. Any number
1257 of Integrity Measurement Collector/Verifier pairs can be attached
1258 via the tnc-imc and tnc-imv charon plugins.
1260 - The IKEv1 daemon pluto now uses the same kernel interfaces as the IKEv2
1261 daemon charon. As a result of this, pluto now supports xfrm marks which
1262 were introduced in charon with 4.4.1.
1264 - Applets for Maemo 5 (Nokia) allow to easily configure and control IKEv2
1265 based VPN connections with EAP authentication on supported devices.
1267 - The RADIUS plugin eap-radius now supports multiple RADIUS servers for
1268 redundant setups. Servers are selected by a defined priority, server load and
1271 - The simple led plugin controls hardware LEDs through the Linux LED subsystem.
1272 It currently shows activity of the IKE daemon and is a good example how to
1273 implement a simple event listener.
1275 - Improved MOBIKE behavior in several corner cases, for instance, if the
1276 initial responder moves to a different address.
1278 - Fixed left-/rightnexthop option, which was broken since 4.4.0.
1280 - Fixed a bug not releasing a virtual IP address to a pool if the XAUTH
1281 identity was different from the IKE identity.
1283 - Fixed the alignment of ModeConfig messages on 4-byte boundaries in the
1284 case where the attributes are not a multiple of 4 bytes (e.g. Cisco's
1287 - Fixed the interoperability of the socket_raw and socket_default
1290 - Added man page for strongswan.conf
1296 - Support of xfrm marks in IPsec SAs and IPsec policies introduced
1297 with the Linux 2.6.34 kernel. For details see the example scenarios
1298 ikev2/nat-two-rw-mark, ikev2/rw-nat-mark-in-out and ikev2/net2net-psk-dscp.
1300 - The PLUTO_MARK_IN and PLUTO_ESP_ENC environment variables can be used
1301 in a user-specific updown script to set marks on inbound ESP or
1304 - The openssl plugin now supports X.509 certificate and CRL functions.
1306 - OCSP/CRL checking in IKEv2 has been moved to the revocation plugin, enabled
1307 by default. Plase update manual load directives in strongswan.conf.
1309 - RFC3779 ipAddrBlock constraint checking has been moved to the addrblock
1310 plugin, disabled by default. Enable it and update manual load directives
1311 in strongswan.conf, if required.
1313 - The pki utility supports CRL generation using the --signcrl command.
1315 - The ipsec pki --self, --issue and --req commands now support output in
1316 PEM format using the --outform pem option.
1318 - The major refactoring of the IKEv1 Mode Config functionality now allows
1319 the transport and handling of any Mode Config attribute.
1321 - The RADIUS proxy plugin eap-radius now supports multiple servers. Configured
1322 servers are chosen randomly, with the option to prefer a specific server.
1323 Non-responding servers are degraded by the selection process.
1325 - The ipsec pool tool manages arbitrary configuration attributes stored
1326 in an SQL database. ipsec pool --help gives the details.
1328 - The new eap-simaka-sql plugin acts as a backend for EAP-SIM and EAP-AKA,
1329 reading triplets/quintuplets from an SQL database.
1331 - The High Availability plugin now supports a HA enabled in-memory address
1332 pool and Node reintegration without IKE_SA rekeying. The latter allows
1333 clients without IKE_SA rekeying support to keep connected during
1334 reintegration. Additionally, many other issues have been fixed in the ha
1337 - Fixed a potential remote code execution vulnerability resulting from
1338 the misuse of snprintf(). The vulnerability is exploitable by
1339 unauthenticated users.
1345 - The IKEv2 High Availability plugin has been integrated. It provides
1346 load sharing and failover capabilities in a cluster of currently two nodes,
1347 based on an extend ClusterIP kernel module. More information is available at
1348 http://wiki.strongswan.org/projects/strongswan/wiki/HighAvailability.
1349 The development of the High Availability functionality was sponsored by
1350 secunet Security Networks AG.
1352 - Added IKEv1 and IKEv2 configuration support for the AES-GMAC
1353 authentication-only ESP cipher. Our aes_gmac kernel patch or a Linux
1354 2.6.34 kernel is required to make AES-GMAC available via the XFRM
1357 - Added support for Diffie-Hellman groups 22, 23 and 24 to the gmp, gcrypt
1358 and openssl plugins, usable by both pluto and charon. The new proposal
1359 keywords are modp1024s160, modp2048s224 and modp2048s256. Thanks to Joy Latten
1360 from IBM for his contribution.
1362 - The IKEv1 pluto daemon supports RAM-based virtual IP pools using
1363 the rightsourceip directive with a subnet from which addresses
1366 - The ipsec pki --gen and --pub commands now allow the output of
1367 private and public keys in PEM format using the --outform pem
1368 command line option.
1370 - The new DHCP plugin queries virtual IP addresses for clients from a DHCP
1371 server using broadcasts, or a defined server using the
1372 charon.plugins.dhcp.server strongswan.conf option. DNS/WINS server information
1373 is additionally served to clients if the DHCP server provides such
1374 information. The plugin is used in ipsec.conf configurations having
1375 rightsourceip set to %dhcp.
1377 - A new plugin called farp fakes ARP responses for virtual IP addresses
1378 handed out to clients from the IKEv2 daemon charon. The plugin lets a
1379 road-warrior act as a client on the local LAN if it uses a virtual IP
1380 from the responders subnet, e.g. acquired using the DHCP plugin.
1382 - The existing IKEv2 socket implementations have been migrated to the
1383 socket-default and the socket-raw plugins. The new socket-dynamic plugin
1384 binds sockets dynamically to ports configured via the left-/rightikeport
1385 ipsec.conf connection parameters.
1387 - The android charon plugin stores received DNS server information as "net.dns"
1388 system properties, as used by the Android platform.
1394 - The IKEv2 daemon supports RFC 3779 IP address block constraints
1395 carried as a critical X.509v3 extension in the peer certificate.
1397 - The ipsec pool --add|del dns|nbns command manages DNS and NBNS name
1398 server entries that are sent via the IKEv1 Mode Config or IKEv2
1399 Configuration Payload to remote clients.
1401 - The Camellia cipher can be used as an IKEv1 encryption algorithm.
1403 - The IKEv1 and IKEV2 daemons now check certificate path length constraints.
1405 - The new ipsec.conf conn option "inactivity" closes a CHILD_SA if no traffic
1406 was sent or received within the given interval. To close the complete IKE_SA
1407 if its only CHILD_SA was inactive, set the global strongswan.conf option
1408 "charon.inactivity_close_ike" to yes.
1410 - More detailed IKEv2 EAP payload information in debug output
1412 - IKEv2 EAP-SIM and EAP-AKA share joint libsimaka library
1414 - Added required userland changes for proper SHA256 and SHA384/512 in ESP that
1415 will be introduced with Linux 2.6.33. The "sha256"/"sha2_256" keyword now
1416 configures the kernel with 128 bit truncation, not the non-standard 96
1417 bit truncation used by previous releases. To use the old 96 bit truncation
1418 scheme, the new "sha256_96" proposal keyword has been introduced.
1420 - Fixed IPComp in tunnel mode, stripping out the duplicated outer header. This
1421 change makes IPcomp tunnel mode connections incompatible with previous
1422 releases; disable compression on such tunnels.
1424 - Fixed BEET mode connections on recent kernels by installing SAs with
1425 appropriate traffic selectors, based on a patch by Michael Rossberg.
1427 - Using extensions (such as BEET mode) and crypto algorithms (such as twofish,
1428 serpent, sha256_96) allocated in the private use space now require that we
1429 know its meaning, i.e. we are talking to strongSwan. Use the new
1430 "charon.send_vendor_id" option in strongswan.conf to let the remote peer know
1433 - Experimental support for draft-eronen-ipsec-ikev2-eap-auth, where the
1434 responder omits public key authentication in favor of a mutual authentication
1435 method. To enable EAP-only authentication, set rightauth=eap on the responder
1436 to rely only on the MSK constructed AUTH payload. This not-yet standardized
1437 extension requires the strongSwan vendor ID introduced above.
1439 - The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus
1440 allowing interoperability.
1446 - The IKEv1 pluto daemon can now use SQL-based address pools to deal out
1447 virtual IP addresses as a Mode Config server. The pool capability has been
1448 migrated from charon's sql plugin to a new attr-sql plugin which is loaded
1449 by libstrongswan and which can be used by both daemons either with a SQLite
1450 or MySQL database and the corresponding plugin.
1452 - Plugin names have been streamlined: EAP plugins now have a dash after eap
1453 (e.g. eap-sim), as it is used with the --enable-eap-sim ./configure option.
1454 Plugin configuration sections in strongswan.conf now use the same name as the
1455 plugin itself (i.e. with a dash). Make sure to update "load" directives and
1456 the affected plugin sections in existing strongswan.conf files.
1458 - The private/public key parsing and encoding has been split up into
1459 separate pkcs1, pgp, pem and dnskey plugins. The public key implementation
1460 plugins gmp, gcrypt and openssl can all make use of them.
1462 - The EAP-AKA plugin can use different backends for USIM/quintuplet
1463 calculations, very similar to the EAP-SIM plugin. The existing 3GPP2 software
1464 implementation has been migrated to a separate plugin.
1466 - The IKEv2 daemon charon gained basic PGP support. It can use locally installed
1467 peer certificates and can issue signatures based on RSA private keys.
1469 - The new 'ipsec pki' tool provides a set of commands to maintain a public
1470 key infrastructure. It currently supports operations to create RSA and ECDSA
1471 private/public keys, calculate fingerprints and issue or verify certificates.
1473 - Charon uses a monotonic time source for statistics and job queueing, behaving
1474 correctly if the system time changes (e.g. when using NTP).
1476 - In addition to time based rekeying, charon supports IPsec SA lifetimes based
1477 on processed volume or number of packets. They new ipsec.conf parameters
1478 'lifetime' (an alias to 'keylife'), 'lifebytes' and 'lifepackets' handle
1479 SA timeouts, while the parameters 'margintime' (an alias to rekeymargin),
1480 'marginbytes' and 'marginpackets' trigger the rekeying before a SA expires.
1481 The existing parameter 'rekeyfuzz' affects all margins.
1483 - If no CA/Gateway certificate is specified in the NetworkManager plugin,
1484 charon uses a set of trusted root certificates preinstalled by distributions.
1485 The directory containing CA certificates can be specified using the
1486 --with-nm-ca-dir=path configure option.
1488 - Fixed the encoding of the Email relative distinguished name in left|rightid
1491 - Fixed the broken parsing of PKCS#7 wrapped certificates by the pluto daemon.
1493 - Fixed smartcard-based authentication in the pluto daemon which was broken by
1494 the ECDSA support introduced with the 4.3.2 release.
1496 - A patch contributed by Heiko Hund fixes mixed IPv6 in IPv4 and vice versa
1497 tunnels established with the IKEv1 pluto daemon.
1499 - The pluto daemon now uses the libstrongswan x509 plugin for certificates and
1500 CRls and the struct id type was replaced by identification_t used by charon
1501 and the libstrongswan library.
1507 - IKEv2 charon daemon ported to FreeBSD and Mac OS X. Installation details can
1508 be found on wiki.strongswan.org.
1510 - ipsec statusall shows the number of bytes transmitted and received over
1511 ESP connections configured by the IKEv2 charon daemon.
1513 - The IKEv2 charon daemon supports include files in ipsec.secrets.
1519 - The configuration option --enable-integrity-test plus the strongswan.conf
1520 option libstrongswan.integrity_test = yes activate integrity tests
1521 of the IKE daemons charon and pluto, libstrongswan and all loaded
1522 plugins. Thus dynamic library misconfigurations and non-malicious file
1523 manipulations can be reliably detected.
1525 - The new default setting libstrongswan.ecp_x_coordinate_only=yes allows
1526 IKEv1 interoperability with MS Windows using the ECP DH groups 19 and 20.
1528 - The IKEv1 pluto daemon now supports the AES-CCM and AES-GCM ESP
1529 authenticated encryption algorithms.
1531 - The IKEv1 pluto daemon now supports V4 OpenPGP keys.
1533 - The RDN parser vulnerability discovered by Orange Labs research team
1534 was not completely fixed in version 4.3.2. Some more modifications
1535 had to be applied to the asn1_length() function to make it robust.
1541 - The new gcrypt plugin provides symmetric cipher, hasher, RNG, Diffie-Hellman
1542 and RSA crypto primitives using the LGPL licensed GNU gcrypt library.
1544 - libstrongswan features an integrated crypto selftest framework for registered
1545 algorithms. The test-vector plugin provides a first set of test vectors and
1546 allows pluto and charon to rely on tested crypto algorithms.
1548 - pluto can now use all libstrongswan plugins with the exception of x509 and xcbc.
1549 Thanks to the openssl plugin, the ECP Diffie-Hellman groups 19, 20, 21, 25, and
1550 26 as well as ECDSA-256, ECDSA-384, and ECDSA-521 authentication can be used
1553 - Applying their fuzzing tool, the Orange Labs vulnerability research team found
1554 another two DoS vulnerabilities, one in the rather old ASN.1 parser of Relative
1555 Distinguished Names (RDNs) and a second one in the conversion of ASN.1 UTCTIME
1556 and GENERALIZEDTIME strings to a time_t value.
1562 - The nm plugin now passes DNS/NBNS server information to NetworkManager,
1563 allowing a gateway administrator to set DNS/NBNS configuration on clients
1566 - The nm plugin also accepts CA certificates for gateway authentication. If
1567 a CA certificate is configured, strongSwan uses the entered gateway address
1568 as its idenitity, requiring the gateways certificate to contain the same as
1569 subjectAltName. This allows a gateway administrator to deploy the same
1570 certificates to Windows 7 and NetworkManager clients.
1572 - The command ipsec purgeike deletes IKEv2 SAs that don't have a CHILD SA.
1573 The command ipsec down <conn>{n} deletes CHILD SA instance n of connection
1574 <conn> whereas ipsec down <conn>{*} deletes all CHILD SA instances.
1575 The command ipsec down <conn>[n] deletes IKE SA instance n of connection
1576 <conn> plus dependent CHILD SAs whereas ipsec down <conn>[*] deletes all
1577 IKE SA instances of connection <conn>.
1579 - Fixed a regression introduced in 4.3.0 where EAP authentication calculated
1580 the AUTH payload incorrectly. Further, the EAP-MSCHAPv2 MSK key derivation
1581 has been updated to be compatible with the Windows 7 Release Candidate.
1583 - Refactored installation of triggering policies. Routed policies are handled
1584 outside of IKE_SAs to keep them installed in any case. A tunnel gets
1585 established only once, even if initiation is delayed due network outages.
1587 - Improved the handling of multiple acquire signals triggered by the kernel.
1589 - Fixed two DoS vulnerabilities in the charon daemon that were discovered by
1590 fuzzing techniques: 1) Sending a malformed IKE_SA_INIT request leaved an
1591 incomplete state which caused a null pointer dereference if a subsequent
1592 CREATE_CHILD_SA request was sent. 2) Sending an IKE_AUTH request with either
1593 a missing TSi or TSr payload caused a null pointer derefence because the
1594 checks for TSi and TSr were interchanged. The IKEv2 fuzzer used was
1595 developed by the Orange Labs vulnerability research team. The tool was
1596 initially written by Gabriel Campana and is now maintained by Laurent Butti.
1598 - Added support for AES counter mode in ESP in IKEv2 using the proposal
1599 keywords aes128ctr, aes192ctr and aes256ctr.
1601 - Further progress in refactoring pluto: Use of the curl and ldap plugins
1602 for fetching crls and OCSP. Use of the random plugin to get keying material
1603 from /dev/random or /dev/urandom. Use of the openssl plugin as an alternative
1604 to the aes, des, sha1, sha2, and md5 plugins. The blowfish, twofish, and
1605 serpent encryption plugins are now optional and are not enabled by default.
1611 - Support for the IKEv2 Multiple Authentication Exchanges extension (RFC4739).
1612 Initiators and responders can use several authentication rounds (e.g. RSA
1613 followed by EAP) to authenticate. The new ipsec.conf leftauth/rightauth and
1614 leftauth2/rightauth2 parameters define own authentication rounds or setup
1615 constraints for the remote peer. See the ipsec.conf man page for more detials.
1617 - If glibc printf hooks (register_printf_function) are not available,
1618 strongSwan can use the vstr string library to run on non-glibc systems.
1620 - The IKEv2 charon daemon can now configure the ESP CAMELLIA-CBC cipher
1621 (esp=camellia128|192|256).
1623 - Refactored the pluto and scepclient code to use basic functions (memory
1624 allocation, leak detective, chunk handling, printf_hooks, strongswan.conf
1625 attributes, ASN.1 parser, etc.) from the libstrongswan library.
1627 - Up to two DNS and WINS servers to be sent via IKEv1 ModeConfig can be
1628 configured in the pluto section of strongswan.conf.
1634 - The new server-side EAP RADIUS plugin (--enable-eap-radius)
1635 relays EAP messages to and from a RADIUS server. Successfully
1636 tested with with a freeradius server using EAP-MD5 and EAP-SIM.
1638 - A vulnerability in the Dead Peer Detection (RFC 3706) code was found by
1639 Gerd v. Egidy <gerd.von.egidy@intra2net.com> of Intra2net AG affecting
1640 all Openswan and strongSwan releases. A malicious (or expired ISAKMP)
1641 R_U_THERE or R_U_THERE_ACK Dead Peer Detection packet can cause the
1642 pluto IKE daemon to crash and restart. No authentication or encryption
1643 is required to trigger this bug. One spoofed UDP packet can cause the
1644 pluto IKE daemon to restart and be unresponsive for a few seconds while
1645 restarting. This DPD null state vulnerability has been officially
1646 registered as CVE-2009-0790 and is fixed by this release.
1648 - ASN.1 to time_t conversion caused a time wrap-around for
1649 dates after Jan 18 03:14:07 UTC 2038 on 32-bit platforms.
1650 As a workaround such dates are set to the maximum representable
1651 time, i.e. Jan 19 03:14:07 UTC 2038.
1653 - Distinguished Names containing wildcards (*) are not sent in the
1654 IDr payload anymore.
1660 - Fixed a use-after-free bug in the DPD timeout section of the
1661 IKEv1 pluto daemon which sporadically caused a segfault.
1663 - Fixed a crash in the IKEv2 charon daemon occurring with
1664 mixed RAM-based and SQL-based virtual IP address pools.
1666 - Fixed ASN.1 parsing of algorithmIdentifier objects where the
1667 parameters field is optional.
1669 - Ported nm plugin to NetworkManager 7.1.
1675 - Support of the EAP-MSCHAPv2 protocol enabled by the option
1676 --enable-eap-mschapv2. Requires the MD4 hash algorithm enabled
1677 either by --enable-md4 or --enable-openssl.
1679 - Assignment of up to two DNS and up to two WINS servers to peers via
1680 the IKEv2 Configuration Payload (CP). The IPv4 or IPv6 nameserver
1681 addresses are defined in strongswan.conf.
1683 - The strongSwan applet for the Gnome NetworkManager is now built and
1684 distributed as a separate tarball under the name NetworkManager-strongswan.
1690 - Fixed ESP NULL encryption broken by the refactoring of keymat.c.
1691 Also introduced proper initialization and disposal of keying material.
1693 - Fixed the missing listing of connection definitions in ipsec statusall
1694 broken by an unfortunate local variable overload.
1700 - Several performance improvements to handle thousands of tunnels with almost
1701 linear upscaling. All relevant data structures have been replaced by faster
1702 counterparts with better lookup times.
1704 - Better parallelization to run charon on multiple cores. Due to improved
1705 resource locking and other optimizations the daemon can take full
1706 advantage of 16 or even more cores.
1708 - The load-tester plugin can use a NULL Diffie-Hellman group and simulate
1709 unique identities and certificates by signing peer certificates using a CA
1712 - The redesigned stroke in-memory IP pool handles leases. The "ipsec leases"
1713 command queries assigned leases.
1715 - Added support for smartcards in charon by using the ENGINE API provided by
1716 OpenSSL, based on patches by Michael Roßberg.
1718 - The Padlock plugin supports the hardware RNG found on VIA CPUs to provide a
1719 reliable source of randomness.
1724 - Flexible configuration of logging subsystem allowing to log to multiple
1725 syslog facilities or to files using fine-grained log levels for each target.
1727 - Load testing plugin to do stress testing of the IKEv2 daemon against self
1728 or another host. Found and fixed issues during tests in the multi-threaded
1729 use of the OpenSSL plugin.
1731 - Added profiling code to synchronization primitives to find bottlenecks if
1732 running on multiple cores. Found and fixed an issue where parts of the
1733 Diffie-Hellman calculation acquired an exclusive lock. This greatly improves
1734 parallelization to multiple cores.
1736 - updown script invocation has been separated into a plugin of its own to
1737 further slim down the daemon core.
1739 - Separated IKE_SA/CHILD_SA key derivation process into a closed system,
1740 allowing future implementations to use a secured environment in e.g. kernel
1743 - The kernel interface of charon has been modularized. XFRM NETLINK (default)
1744 and PFKEY (--enable-kernel-pfkey) interface plugins for the native IPsec
1745 stack of the Linux 2.6 kernel as well as a PFKEY interface for the KLIPS
1746 IPsec stack (--enable-kernel-klips) are provided.
1748 - Basic Mobile IPv6 support has been introduced, securing Binding Update
1749 messages as well as tunneled traffic between Mobile Node and Home Agent.
1750 The installpolicy=no option allows peaceful cooperation with a dominant
1751 mip6d daemon and the new type=transport_proxy implements the special MIPv6
1752 IPsec transport proxy mode where the IKEv2 daemon uses the Care-of-Address
1753 but the IPsec SA is set up for the Home Address.
1755 - Implemented migration of Mobile IPv6 connections using the KMADDRESS
1756 field contained in XFRM_MSG_MIGRATE messages sent by the mip6d daemon
1757 via the Linux 2.6.28 (or appropriately patched) kernel.
1763 - IKEv2 charon daemon supports authentication based on raw public keys
1764 stored in the SQL database backend. The ipsec listpubkeys command
1765 lists the available raw public keys via the stroke interface.
1767 - Several MOBIKE improvements: Detect changes in NAT mappings in DPD exchanges,
1768 handle events if kernel detects NAT mapping changes in UDP-encapsulated
1769 ESP packets (requires kernel patch), reuse old addesses in MOBIKE updates as
1770 long as possible and other fixes.
1772 - Fixed a bug in addr_in_subnet() which caused insertion of wrong source
1773 routes for destination subnets having netwmasks not being a multiple of 8 bits.
1774 Thanks go to Wolfgang Steudel, TU Ilmenau for reporting this bug.
1780 - Fixed a Denial-of-Service vulnerability where an IKE_SA_INIT message with
1781 a KE payload containing zeroes only can cause a crash of the IKEv2 charon
1782 daemon due to a NULL pointer returned by the mpz_export() function of the
1783 GNU Multiprecision Library (GMP). Thanks go to Mu Dynamics Research Labs
1784 for making us aware of this problem.
1786 - The new agent plugin provides a private key implementation on top of an
1789 - The NetworkManager plugin has been extended to support certificate client
1790 authentication using RSA keys loaded from a file or using ssh-agent.
1792 - Daemon capability dropping has been ported to libcap and must be enabled
1793 explicitly --with-capabilities=libcap. Future version will support the
1794 newer libcap2 library.
1796 - ipsec listalgs lists the IKEv2 cryptografic algorithms registered with the
1797 charon keying daemon.
1803 - A NetworkManager plugin allows GUI-based configuration of road-warrior
1804 clients in a simple way. It features X509 based gateway authentication
1805 and EAP client authentication, tunnel setup/teardown and storing passwords
1806 in the Gnome Keyring.
1808 - A new EAP-GTC plugin implements draft-sheffer-ikev2-gtc-00.txt and allows
1809 username/password authentication against any PAM service on the gateway.
1810 The new EAP method interacts nicely with the NetworkManager plugin and allows
1811 client authentication against e.g. LDAP.
1813 - Improved support for the EAP-Identity method. The new ipsec.conf eap_identity
1814 parameter defines an additional identity to pass to the server in EAP
1817 - The "ipsec statusall" command now lists CA restrictions, EAP
1818 authentication types and EAP identities.
1820 - Fixed two multithreading deadlocks occurring when starting up
1821 several hundred tunnels concurrently.
1823 - Fixed the --enable-integrity-test configure option which
1824 computes a SHA-1 checksum over the libstrongswan library.
1830 - Consistent logging of IKE and CHILD SAs at the audit (AUD) level.
1832 - Improved the performance of the SQL-based virtual IP address pool
1833 by introducing an additional addresses table. The leases table
1834 storing only history information has become optional and can be
1835 disabled by setting charon.plugins.sql.lease_history = no in
1838 - The XFRM_STATE_AF_UNSPEC flag added to xfrm.h allows IPv4-over-IPv6
1839 and IPv6-over-IPv4 tunnels with the 2.6.26 and later Linux kernels.
1841 - management of different virtual IP pools for different
1842 network interfaces have become possible.
1844 - fixed a bug which prevented the assignment of more than 256
1845 virtual IP addresses from a pool managed by an sql database.
1847 - fixed a bug which did not delete own IPCOMP SAs in the kernel.
1853 - Added statistics functions to ipsec pool --status and ipsec pool --leases
1854 and input validation checks to various ipsec pool commands.
1856 - ipsec statusall now lists all loaded charon plugins and displays
1857 the negotiated IKEv2 cipher suite proposals.
1859 - The openssl plugin supports the elliptic curve Diffie-Hellman groups
1860 19, 20, 21, 25, and 26.
1862 - The openssl plugin supports ECDSA authentication using elliptic curve
1865 - Fixed a bug in stroke which caused multiple charon threads to close
1866 the file descriptors during packet transfers over the stroke socket.
1868 - ESP sequence numbers are now migrated in IPsec SA updates handled by
1869 MOBIKE. Works only with Linux kernels >= 2.6.17.
1875 - Fixed the strongswan.conf path configuration problem that occurred when
1876 --sysconfig was not set explicitly in ./configure.
1878 - Fixed a number of minor bugs that where discovered during the 4th
1879 IKEv2 interoperability workshop in San Antonio, TX.
1885 - Plugins for libstrongswan and charon can optionally be loaded according
1886 to a configuration in strongswan.conf. Most components provide a
1887 "load = " option followed by a space separated list of plugins to load.
1888 This allows e.g. the fallback from a hardware crypto accelerator to
1889 to software-based crypto plugins.
1891 - Charons SQL plugin has been extended by a virtual IP address pool.
1892 Configurations with a rightsourceip=%poolname setting query a SQLite or
1893 MySQL database for leases. The "ipsec pool" command helps in administrating
1894 the pool database. See ipsec pool --help for the available options
1896 - The Authenticated Encryption Algorithms AES-CCM-8/12/16 and AES-GCM-8/12/16
1897 for ESP are now supported starting with the Linux 2.6.25 kernel. The
1898 syntax is e.g. esp=aes128ccm12 or esp=aes256gcm16.
1904 - Support for "Hash and URL" encoded certificate payloads has been implemented
1905 in the IKEv2 daemon charon. Using the "certuribase" option of a CA section
1906 allows to assign a base URL to all certificates issued by the specified CA.
1907 The final URL is then built by concatenating that base and the hex encoded
1908 SHA1 hash of the DER encoded certificate. Note that this feature is disabled
1909 by default and must be enabled using the option "charon.hash_and_url".
1911 - The IKEv2 daemon charon now supports the "uniqueids" option to close multiple
1912 IKE_SAs with the same peer. The option value "keep" prefers existing
1913 connection setups over new ones, where the value "replace" replaces existing
1916 - The crypto factory in libstrongswan additionally supports random number
1917 generators, plugins may provide other sources of randomness. The default
1918 plugin reads raw random data from /dev/(u)random.
1920 - Extended the credential framework by a caching option to allow plugins
1921 persistent caching of fetched credentials. The "cachecrl" option has been
1924 - The new trustchain verification introduced in 4.2.0 has been parallelized.
1925 Threads fetching CRL or OCSP information no longer block other threads.
1927 - A new IKEv2 configuration attribute framework has been introduced allowing
1928 plugins to provide virtual IP addresses, and in the future, other
1929 configuration attribute services (e.g. DNS/WINS servers).
1931 - The stroke plugin has been extended to provide virtual IP addresses from
1932 a pool defined in ipsec.conf. The "rightsourceip" parameter now accepts
1933 address pools in CIDR notation (e.g. 10.1.1.0/24). The parameter also accepts
1934 the value "%poolname", where "poolname" identifies a pool provided by a
1937 - Fixed compilation on uClibc and a couple of other minor bugs.
1939 - Set DPD defaults in ipsec starter to dpd_delay=30s and dpd_timeout=150s.
1941 - The IKEv1 pluto daemon now supports the ESP encryption algorithm CAMELLIA
1942 with key lengths of 128, 192, and 256 bits, as well as the authentication
1943 algorithm AES_XCBC_MAC. Configuration example: esp=camellia192-aesxcbc.
1949 - libstrongswan has been modularized to attach crypto algorithms,
1950 credential implementations (keys, certificates) and fetchers dynamically
1951 through plugins. Existing code has been ported to plugins:
1952 - RSA/Diffie-Hellman implementation using the GNU Multi Precision library
1953 - X509 certificate system supporting CRLs, OCSP and attribute certificates
1954 - Multiple plugins providing crypto algorithms in software
1955 - CURL and OpenLDAP fetcher
1957 - libstrongswan gained a relational database API which uses pluggable database
1958 providers. Plugins for MySQL and SQLite are available.
1960 - The IKEv2 keying daemon charon is more extensible. Generic plugins may provide
1961 connection configuration, credentials and EAP methods or control the daemon.
1962 Existing code has been ported to plugins:
1963 - EAP-AKA, EAP-SIM, EAP-MD5 and EAP-Identity
1964 - stroke configuration, credential and control (compatible to pluto)
1965 - XML bases management protocol to control and query the daemon
1966 The following new plugins are available:
1967 - An experimental SQL configuration, credential and logging plugin on
1968 top of either MySQL or SQLite
1969 - A unit testing plugin to run tests at daemon startup
1971 - The authentication and credential framework in charon has been heavily
1972 refactored to support modular credential providers, proper
1973 CERTREQ/CERT payload exchanges and extensible authorization rules.
1975 - The framework of strongSwan Manager has envolved to the web application
1976 framework libfast (FastCGI Application Server w/ Templates) and is usable
1977 by other applications.
1983 - IKE rekeying in NAT situations did not inherit the NAT conditions
1984 to the rekeyed IKE_SA so that the UDP encapsulation was lost with
1985 the next CHILD_SA rekeying.
1987 - Wrong type definition of the next_payload variable in id_payload.c
1988 caused an INVALID_SYNTAX error on PowerPC platforms.
1990 - Implemented IKEv2 EAP-SIM server and client test modules that use
1991 triplets stored in a file. For details on the configuration see
1992 the scenario 'ikev2/rw-eap-sim-rsa'.
1998 - Fixed error in the ordering of the certinfo_t records in the ocsp cache that
1999 caused multiple entries of the same serial number to be created.
2001 - Implementation of a simple EAP-MD5 module which provides CHAP
2002 authentication. This may be interesting in conjunction with certificate
2003 based server authentication, as weak passwords can't be brute forced
2004 (in contradiction to traditional IKEv2 PSK).
2006 - A complete software based implementation of EAP-AKA, using algorithms
2007 specified in 3GPP2 (S.S0055). This implementation does not use an USIM,
2008 but reads the secrets from ipsec.secrets. Make sure to read eap_aka.h
2011 - Support for vendor specific EAP methods using Expanded EAP types. The
2012 interface to EAP modules has been slightly changed, so make sure to
2013 check the changes if you're already rolling your own modules.
2019 - The default _updown script now dynamically inserts and removes ip6tables
2020 firewall rules if leftfirewall=yes is set in IPv6 connections. New IPv6
2021 net-net and roadwarrior (PSK/RSA) scenarios for both IKEv1 and IKEV2 were
2024 - Implemented RFC4478 repeated authentication to force EAP/Virtual-IP clients
2025 to reestablish an IKE_SA within a given timeframe.
2027 - strongSwan Manager supports configuration listing, initiation and termination
2028 of IKE and CHILD_SAs.
2030 - Fixes and improvements to multithreading code.
2032 - IKEv2 plugins have been renamed to libcharon-* to avoid naming conflicts.
2033 Make sure to remove the old plugins in $libexecdir/ipsec, otherwise they get
2040 - Removed recursive pthread mutexes since uClibc doesn't support them.
2046 - In NAT traversal situations and multiple queued Quick Modes,
2047 those pending connections inserted by auto=start after the
2048 port floating from 500 to 4500 were erronously deleted.
2050 - Added a "forceencaps" connection parameter to enforce UDP encapsulation
2051 to surmount restrictive firewalls. NAT detection payloads are faked to
2052 simulate a NAT situation and trick the other peer into NAT mode (IKEv2 only).
2054 - Preview of strongSwan Manager, a web based configuration and monitoring
2055 application. It uses a new XML control interface to query the IKEv2 daemon
2056 (see http://wiki.strongswan.org/wiki/Manager).
2058 - Experimental SQLite configuration backend which will provide the configuration
2059 interface for strongSwan Manager in future releases.
2061 - Further improvements to MOBIKE support.
2067 - Since some third party IKEv2 implementations run into
2068 problems with strongSwan announcing MOBIKE capability per
2069 default, MOBIKE can be disabled on a per-connection-basis
2070 using the mobike=no option. Whereas mobike=no disables the
2071 sending of the MOBIKE_SUPPORTED notification and the floating
2072 to UDP port 4500 with the IKE_AUTH request even if no NAT
2073 situation has been detected, strongSwan will still support
2074 MOBIKE acting as a responder.
2076 - the default ipsec routing table plus its corresponding priority
2077 used for inserting source routes has been changed from 100 to 220.
2078 It can be configured using the --with-ipsec-routing-table and
2079 --with-ipsec-routing-table-prio options.
2081 - the --enable-integrity-test configure option tests the
2082 integrity of the libstrongswan crypto code during the charon
2085 - the --disable-xauth-vid configure option disables the sending
2086 of the XAUTH vendor ID. This can be used as a workaround when
2087 interoperating with some Windows VPN clients that get into
2088 trouble upon reception of an XAUTH VID without eXtended
2089 AUTHentication having been configured.
2091 - ipsec stroke now supports the rereadsecrets, rereadaacerts,
2092 rereadacerts, and listacerts options.
2098 - If a DNS lookup failure occurs when resolving right=%<FQDN>
2099 or right=<FQDN> combined with rightallowany=yes then the
2100 connection is not updated by ipsec starter thus preventing
2101 the disruption of an active IPsec connection. Only if the DNS
2102 lookup successfully returns with a changed IP address the
2103 corresponding connection definition is updated.
2105 - Routes installed by the keying daemons are now in a separate
2106 routing table with the ID 100 to avoid conflicts with the main
2107 table. Route lookup for IKEv2 traffic is done in userspace to ignore
2108 routes installed for IPsec, as IKE traffic shouldn't get encapsulated.
2114 - The pluto IKEv1 daemon now exhibits the same behaviour as its
2115 IKEv2 companion charon by inserting an explicit route via the
2116 _updown script only if a sourceip exists. This is admissible
2117 since routing through the IPsec tunnel is handled automatically
2118 by NETKEY's IPsec policies. As a consequence the left|rightnexthop
2119 parameter is not required any more.
2121 - The new IKEv1 parameter right|leftallowany parameters helps to handle
2122 the case where both peers possess dynamic IP addresses that are
2123 usually resolved using DynDNS or a similar service. The configuration
2128 can be used by the initiator to start up a connection to a peer
2129 by resolving peer.foo.bar into the currently allocated IP address.
2130 Thanks to the rightallowany flag the connection behaves later on
2135 so that the peer can rekey the connection as an initiator when his
2136 IP address changes. An alternative notation is
2140 which will implicitly set rightallowany=yes.
2142 - ipsec starter now fails more gracefully in the presence of parsing
2143 errors. Flawed ca and conn section are discarded and pluto is started
2144 if non-fatal errors only were encountered. If right=%peer.foo.bar
2145 cannot be resolved by DNS then right=%any will be used so that passive
2146 connections as a responder are still possible.
2148 - The new pkcs11initargs parameter that can be placed in the
2149 setup config section of /etc/ipsec.conf allows the definition
2150 of an argument string that is used with the PKCS#11 C_Initialize()
2151 function. This non-standard feature is required by the NSS softoken
2152 library. This patch was contributed by Robert Varga.
2154 - Fixed a bug in ipsec starter introduced by strongswan-2.8.5
2155 which caused a segmentation fault in the presence of unknown
2156 or misspelt keywords in ipsec.conf. This bug fix was contributed
2159 - Partial support for MOBIKE in IKEv2. The initiator acts on interface/
2160 address configuration changes and updates IKE and IPsec SAs dynamically.
2166 - IKEv2 peer configuration selection now can be based on a given
2167 certification authority using the rightca= statement.
2169 - IKEv2 authentication based on RSA signatures now can handle multiple
2170 certificates issued for a given peer ID. This allows a smooth transition
2171 in the case of a peer certificate renewal.
2173 - IKEv2: Support for requesting a specific virtual IP using leftsourceip on the
2174 client and returning requested virtual IPs using rightsourceip=%config
2175 on the server. If the server does not support configuration payloads, the
2176 client enforces its leftsourceip parameter.
2178 - The ./configure options --with-uid/--with-gid allow pluto and charon
2179 to drop their privileges to a minimum and change to an other UID/GID. This
2180 improves the systems security, as a possible intruder may only get the
2181 CAP_NET_ADMIN capability.
2183 - Further modularization of charon: Pluggable control interface and
2184 configuration backend modules provide extensibility. The control interface
2185 for stroke is included, and further interfaces using DBUS (NetworkManager)
2186 or XML are on the way. A backend for storing configurations in the daemon
2187 is provided and more advanced backends (using e.g. a database) are trivial
2190 - Fixed a compilation failure in libfreeswan occurring with Linux kernel
2197 - Support for an additional Diffie-Hellman exchange when creating/rekeying
2198 a CHILD_SA in IKEv2 (PFS). PFS is enabled when the proposal contains a
2199 DH group (e.g. "esp=aes128-sha1-modp1536"). Further, DH group negotiation
2200 is implemented properly for rekeying.
2202 - Support for the AES-XCBC-96 MAC algorithm for IPsec SAs when using IKEv2
2203 (requires linux >= 2.6.20). It is enabled using e.g. "esp=aes256-aesxcbc".
2205 - Working IPv4-in-IPv6 and IPv6-in-IPv4 tunnels for linux >= 2.6.21.
2207 - Added support for EAP modules which do not establish an MSK.
2209 - Removed the dependencies from the /usr/include/linux/ headers by
2210 including xfrm.h, ipsec.h, and pfkeyv2.h in the distribution.
2212 - crlNumber is now listed by ipsec listcrls
2214 - The xauth_modules.verify_secret() function now passes the
2221 - Server side cookie support. If to may IKE_SAs are in CONNECTING state,
2222 cookies are enabled and protect against DoS attacks with faked source
2223 addresses. Number of IKE_SAs in CONNECTING state is also limited per
2224 peer address to avoid resource exhaustion. IKE_SA_INIT messages are
2225 compared to properly detect retransmissions and incoming retransmits are
2226 detected even if the IKE_SA is blocked (e.g. doing OCSP fetches).
2228 - The IKEv2 daemon charon now supports dynamic http- and ldap-based CRL
2229 fetching enabled by crlcheckinterval > 0 and caching fetched CRLs
2230 enabled by cachecrls=yes.
2232 - Added the configuration options --enable-nat-transport which enables
2233 the potentially insecure NAT traversal for IPsec transport mode and
2234 --disable-vendor-id which disables the sending of the strongSwan
2237 - Fixed a long-standing bug in the pluto IKEv1 daemon which caused
2238 a segmentation fault if a malformed payload was detected in the
2239 IKE MR2 message and pluto tried to send an encrypted notification
2242 - Added the NATT_IETF_02_N Vendor ID in order to support IKEv1 connections
2243 with Windows 2003 Server which uses a wrong VID hash.
2249 - Support of SHA2_384 hash function for protecting IKEv1
2250 negotiations and support of SHA2 signatures in X.509 certificates.
2252 - Fixed a serious bug in the computation of the SHA2-512 HMAC
2253 function. Introduced automatic self-test of all IKEv1 hash
2254 and hmac functions during pluto startup. Failure of a self-test
2255 currently issues a warning only but does not exit pluto [yet].
2257 - Support for SHA2-256/384/512 PRF and HMAC functions in IKEv2.
2259 - Full support of CA information sections. ipsec listcainfos
2260 now shows all collected crlDistributionPoints and OCSP
2263 - Support of the Online Certificate Status Protocol (OCSP) for IKEv2.
2264 This feature requires the HTTP fetching capabilities of the libcurl
2265 library which must be enabled by setting the --enable-http configure
2268 - Refactored core of the IKEv2 message processing code, allowing better
2269 code reuse and separation.
2271 - Virtual IP support in IKEv2 using INTERNAL_IP4/6_ADDRESS configuration
2272 payload. Additionally, the INTERNAL_IP4/6_DNS attribute is interpreted
2273 by the requestor and installed in a resolv.conf file.
2275 - The IKEv2 daemon charon installs a route for each IPsec policy to use
2276 the correct source address even if an application does not explicitly
2279 - Integrated the EAP framework into charon which loads pluggable EAP library
2280 modules. The ipsec.conf parameter authby=eap initiates EAP authentication
2281 on the client side, while the "eap" parameter on the server side defines
2282 the EAP method to use for client authentication.
2283 A generic client side EAP-Identity module and an EAP-SIM authentication
2284 module using a third party card reader implementation are included.
2286 - Added client side support for cookies.
2288 - Integrated the fixes done at the IKEv2 interoperability bakeoff, including
2289 strict payload order, correct INVALID_KE_PAYLOAD rejection and other minor
2290 fixes to enhance interoperability with other implementations.
2296 - strongSwan now interoperates with the NCP Secure Entry Client,
2297 the Shrew Soft VPN Client, and the Cisco VPN client, doing both
2298 XAUTH and Mode Config.
2300 - UNITY attributes are now recognized and UNITY_BANNER is set
2301 to a default string.
2307 - IKEv1: Support for extended authentication (XAUTH) in combination
2308 with ISAKMP Main Mode RSA or PSK authentication. Both client and
2309 server side were implemented. Handling of user credentials can
2310 be done by a run-time loadable XAUTH module. By default user
2311 credentials are stored in ipsec.secrets.
2313 - IKEv2: Support for reauthentication when rekeying
2315 - IKEv2: Support for transport mode
2317 - fixed a lot of bugs related to byte order
2319 - various other bugfixes
2325 - IKEv1: Implementation of ModeConfig push mode via the new connection
2326 keyword modeconfig=push allows interoperability with Cisco VPN gateways.
2328 - IKEv1: The command ipsec statusall now shows "DPD active" for all
2329 ISAKMP SAs that are under active Dead Peer Detection control.
2331 - IKEv2: Charon's logging and debugging framework has been completely rewritten.
2332 Instead of logger, special printf() functions are used to directly
2333 print objects like hosts (%H) identifications (%D), certificates (%Q),
2334 etc. The number of debugging levels have been reduced to:
2336 0 (audit), 1 (control), 2 (controlmore), 3 (raw), 4 (private)
2338 The debugging levels can either be specified statically in ipsec.conf as
2341 charondebug="lib 1, cfg 3, net 2"
2343 or changed at runtime via stroke as
2345 ipsec stroke loglevel cfg 2
2351 - Implemented full support for IPv6-in-IPv6 tunnels.
2353 - Added configuration options for dead peer detection in IKEv2. dpd_action
2354 types "clear", "hold" and "restart" are supported. The dpd_timeout
2355 value is not used, as the normal retransmission policy applies to
2356 detect dead peers. The dpd_delay parameter enables sending of empty
2357 informational message to detect dead peers in case of inactivity.
2359 - Added support for preshared keys in IKEv2. PSK keys configured in
2360 ipsec.secrets are loaded. The authby parameter specifies the authentication
2361 method to authentificate ourself, the other peer may use PSK or RSA.
2363 - Changed retransmission policy to respect the keyingtries parameter.
2365 - Added private key decryption. PEM keys encrypted with AES-128/192/256
2366 or 3DES are supported.
2368 - Implemented DES/3DES algorithms in libstrongswan. 3DES can be used to
2369 encrypt IKE traffic.
2371 - Implemented SHA-256/384/512 in libstrongswan, allows usage of certificates
2372 signed with such a hash algorithm.
2374 - Added initial support for updown scripts. The actions up-host/client and
2375 down-host/client are executed. The leftfirewall=yes parameter
2376 uses the default updown script to insert dynamic firewall rules, a custom
2377 updown script may be specified with the leftupdown parameter.
2383 - Added support for the auto=route ipsec.conf parameter and the
2384 ipsec route/unroute commands for IKEv2. This allows to set up IKE_SAs and
2385 CHILD_SAs dynamically on demand when traffic is detected by the
2388 - Added support for rekeying IKE_SAs in IKEv2 using the ikelifetime parameter.
2389 As specified in IKEv2, no reauthentication is done (unlike in IKEv1), only
2390 new keys are generated using perfect forward secrecy. An optional flag
2391 which enforces reauthentication will be implemented later.
2393 - "sha" and "sha1" are now treated as synonyms in the ike= and esp=
2394 algorithm configuration statements.
2400 - Full X.509 certificate trust chain verification has been implemented.
2401 End entity certificates can be exchanged via CERT payloads. The current
2402 default is leftsendcert=always, since CERTREQ payloads are not supported
2403 yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls.
2405 - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2
2406 would offer more possibilities for traffic selection, but the Linux kernel
2407 currently does not support it. That's why we stick with these simple
2408 ipsec.conf rules for now.
2410 - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no
2411 IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear,
2414 - Initial NAT traversal support in IKEv2. Charon includes NAT detection
2415 notify payloads to detect NAT routers between the peers. It switches
2416 to port 4500, uses UDP encapsulated ESP packets, handles peer address
2417 changes gracefully and sends keep alive message periodically.
2419 - Reimplemented IKE_SA state machine for charon, which allows simultaneous
2420 rekeying, more shared code, cleaner design, proper retransmission
2421 and a more extensible code base.
2423 - The mixed PSK/RSA roadwarrior detection capability introduced by the
2424 strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal
2425 payloads by the responder right before any defined IKE Main Mode state had
2426 been established. Although any form of bad proposal syntax was being correctly
2427 detected by the payload parser, the subsequent error handler didn't check
2428 the state pointer before logging current state information, causing an
2429 immediate crash of the pluto keying daemon due to a NULL pointer.
2435 - Added algorithm selection to charon: New default algorithms for
2436 ike=aes128-sha-modp2048, as both daemons support it. The default
2437 for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles
2438 the ike/esp parameter the same way as pluto. As this syntax does
2439 not allow specification of a pseudo random function, the same
2440 algorithm as for integrity is used (currently sha/md5). Supported
2442 Encryption: aes128, aes192, aes256
2443 Integrity/PRF: md5, sha (using hmac)
2444 DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192
2446 Encryption: aes128, aes192, aes256, 3des, blowfish128,
2447 blowfish192, blowfish256
2448 Integrity: md5, sha1
2449 More IKE encryption algorithms will come after porting libcrypto into
2452 - initial support for rekeying CHILD_SAs using IKEv2. Currently no
2453 perfect forward secrecy is used. The rekeying parameters rekey,
2454 rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported
2455 when using IKEv2. WARNING: charon currently is unable to handle
2456 simultaneous rekeying. To avoid such a situation, use a large
2457 rekeyfuzz, or even better, set rekey=no on one peer.
2459 - support for host2host, net2net, host2net (roadwarrior) tunnels
2460 using predefined RSA certificates (see uml scenarios for
2461 configuration examples).
2463 - new build environment featuring autotools. Features such
2464 as HTTP, LDAP and smartcard support may be enabled using
2465 the ./configure script. Changing install directories
2466 is possible, too. See ./configure --help for more details.
2468 - better integration of charon with ipsec starter, which allows
2469 (almost) transparent operation with both daemons. charon
2470 handles ipsec commands up, down, status, statusall, listall,
2471 listcerts and allows proper load, reload and delete of connections
2478 - initial support of the IKEv2 protocol. Connections in
2479 ipsec.conf designated by keyexchange=ikev2 are negotiated
2480 by the new IKEv2 charon keying daemon whereas those marked
2481 by keyexchange=ikev1 or the default keyexchange=ike are
2482 handled thy the IKEv1 pluto keying daemon. Currently only
2483 a limited subset of functions are available with IKEv2
2484 (Default AES encryption, authentication based on locally
2485 imported X.509 certificates, unencrypted private RSA keys
2486 in PKCS#1 file format, limited functionality of the ipsec
2493 - the dynamic iptables rules from the _updown_x509 template
2494 for KLIPS and the _updown_policy template for NETKEY have
2495 been merged into the default _updown script. The existing
2496 left|rightfirewall keyword causes the automatic insertion
2497 and deletion of ACCEPT rules for tunneled traffic upon
2498 the successful setup and teardown of an IPsec SA, respectively.
2499 left|rightfirwall can be used with KLIPS under any Linux 2.4
2500 kernel or with NETKEY under a Linux kernel version >= 2.6.16
2501 in conjunction with iptables >= 1.3.5. For NETKEY under a Linux
2502 kernel version < 2.6.16 which does not support IPsec policy
2503 matching yet, please continue to use a copy of the _updown_espmark
2504 template loaded via the left|rightupdown keyword.
2506 - a new left|righthostaccess keyword has been introduced which
2507 can be used in conjunction with left|rightfirewall and the
2508 default _updown script. By default leftfirewall=yes inserts
2509 a bi-directional iptables FORWARD rule for a local client network
2510 with a netmask different from 255.255.255.255 (single host).
2511 This does not allow to access the VPN gateway host via its
2512 internal network interface which is part of the client subnet
2513 because an iptables INPUT and OUTPUT rule would be required.
2514 lefthostaccess=yes will cause this additional ACCEPT rules to
2517 - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal
2518 payload is preparsed in order to find out whether the roadwarrior
2519 requests PSK or RSA so that a matching connection candidate can
2526 - the new _updown_policy template allows ipsec policy based
2527 iptables firewall rules. Required are iptables version
2528 >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes
2529 the _updown_espmark template, so that no INPUT mangle rules
2530 are required any more.
2532 - added support of DPD restart mode
2534 - ipsec starter now allows the use of wildcards in include
2535 statements as e.g. in "include /etc/my_ipsec/*.conf".
2536 Patch courtesy of Matthias Haas.
2538 - the Netscape OID 'employeeNumber' is now recognized and can be
2539 used as a Relative Distinguished Name in certificates.
2545 - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec
2546 command and not of ipsec setup any more.
2548 - ipsec starter now supports AH authentication in conjunction with
2549 ESP encryption. AH authentication is configured in ipsec.conf
2550 via the auth=ah parameter.
2552 - The command ipsec scencrypt|scdecrypt <args> is now an alias for
2553 ipsec whack --scencrypt|scdecrypt <args>.
2555 - get_sa_info() now determines for the native netkey IPsec stack
2556 the exact time of the last use of an active eroute. This information
2557 is used by the Dead Peer Detection algorithm and is also displayed by
2558 the ipsec status command.
2564 - running under the native Linux 2.6 IPsec stack, the function
2565 get_sa_info() is called by ipsec auto --status to display the current
2566 number of transmitted bytes per IPsec SA.
2568 - get_sa_info() is also used by the Dead Peer Detection process to detect
2569 recent ESP activity. If ESP traffic was received from the peer within
2570 the last dpd_delay interval then no R_Y_THERE notification must be sent.
2572 - strongSwan now supports the Relative Distinguished Name "unstructuredName"
2573 in ID_DER_ASN1_DN identities. The following notations are possible:
2575 rightid="unstructuredName=John Doe"
2576 rightid="UN=John Doe"
2578 - fixed a long-standing bug which caused PSK-based roadwarrior connections
2579 to segfault in the function id.c:same_id() called by keys.c:get_secret()
2580 if an FQDN, USER_FQDN, or Key ID was defined, as in the following example.
2587 - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall).
2589 - ipsec starter didn't set host_addr and client.addr ports in whack msg.
2591 - in order to guarantee backwards-compatibility with the script-based
2592 auto function (e.g. auto --replace), the ipsec starter scripts stores
2593 the defaultroute information in the temporary file /var/run/ipsec.info.
2595 - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH
2596 Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config
2599 - the ipsec starter now also recognizes the parameters authby=never and
2600 type=passthrough|pass|drop|reject.
2606 - ipsec starter now supports the also parameter which allows
2607 a modular structure of the connection definitions. Thus
2608 "ipsec start" is now ready to replace "ipsec setup".
2614 - Mathieu Lafon's popular ipsec starter tool has been added to the
2615 strongSwan distribution. Many thanks go to Stephan Scholz from astaro
2616 for his integration work. ipsec starter is a C program which is going
2617 to replace the various shell and awk starter scripts (setup, _plutoload,
2618 _plutostart, _realsetup, _startklips, _confread, and auto). Since
2619 ipsec.conf is now parsed only once, the starting of multiple tunnels is
2620 accelerated tremedously.
2622 - Added support of %defaultroute to the ipsec starter. If the IP address
2623 changes, a HUP signal to the ipsec starter will automatically
2624 reload pluto's connections.
2626 - moved most compile time configurations from pluto/Makefile to
2627 Makefile.inc by defining the options USE_LIBCURL, USE_LDAP,
2628 USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE.
2630 - removed the ipsec verify and ipsec newhostkey commands
2632 - fixed some 64-bit issues in formatted print statements
2634 - The scepclient functionality implementing the Simple Certificate
2635 Enrollment Protocol (SCEP) is nearly complete but hasn't been
2642 - CA certicates are now automatically loaded from a smartcard
2643 or USB crypto token and appear in the ipsec auto --listcacerts
2650 - when using "ipsec whack --scencrypt <data>" with a PKCS#11
2651 library that does not support the C_Encrypt() Cryptoki
2652 function (e.g. OpenSC), the RSA encryption is done in
2653 software using the public key fetched from the smartcard.
2655 - The scepclient function now allows to define the
2656 validity of a self-signed certificate using the --days,
2657 --startdate, and --enddate options. The default validity
2658 has been changed from one year to five years.
2664 - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11
2665 interface to other applications for RSA encryption and decryption
2666 via the whack interface. Notation:
2668 ipsec whack --scencrypt <data>
2669 [--inbase 16|hex|64|base64|256|text|ascii]
2670 [--outbase 16|hex|64|base64|256|text|ascii]
2673 ipsec whack --scdecrypt <data>
2674 [--inbase 16|hex|64|base64|256|text|ascii]
2675 [--outbase 16|hex|64|base64|256|text|ascii]
2678 The default setting for inbase and outbase is hex.
2680 The new proxy interface can be used for securing symmetric
2681 encryption keys required by the cryptoloop or dm-crypt
2682 disk encryption schemes, especially in the case when
2683 pkcs11keepstate=yes causes pluto to lock the pkcs11 slot
2686 - if the file /etc/ipsec.secrets is lacking during the startup of
2687 pluto then the root-readable file /etc/ipsec.d/private/myKey.der
2688 containing a 2048 bit RSA private key and a matching self-signed
2689 certificate stored in the file /etc/ipsec.d/certs/selfCert.der
2690 is automatically generated by calling the function
2692 ipsec scepclient --out pkcs1 --out cert-self
2694 scepclient was written by Jan Hutter and Martin Willi, students
2695 at the University of Applied Sciences in Rapperswil, Switzerland.
2701 - the current extension of the PKCS#7 framework introduced
2702 a parsing error in PKCS#7 wrapped X.509 certificates that are
2703 e.g. transmitted by Windows XP when multi-level CAs are used.
2704 the parsing syntax has been fixed.
2706 - added a patch by Gerald Richter which tolerates multiple occurrences
2707 of the ipsec0 interface when using KLIPS.
2713 - with gawk-3.1.4 the word "default2 has become a protected
2714 keyword for use in switch statements and cannot be used any
2715 more in the strongSwan scripts. This problem has been
2716 solved by renaming "default" to "defaults" and "setdefault"
2717 in the scripts _confread and auto, respectively.
2719 - introduced the parameter leftsendcert with the values
2721 always|yes (the default, always send a cert)
2722 ifasked (send the cert only upon a cert request)
2723 never|no (never send a cert, used for raw RSA keys and
2726 - fixed the initialization of the ESP key length to a default of
2727 128 bits in the case that the peer does not send a key length
2728 attribute for AES encryption.
2730 - applied Herbert Xu's uniqueIDs patch
2732 - applied Herbert Xu's CLOEXEC patches
2738 - CRLs can now be cached also in the case when the issuer's
2739 certificate does not contain a subjectKeyIdentifier field.
2740 In that case the subjectKeyIdentifier is computed by pluto as the
2741 160 bit SHA-1 hash of the issuer's public key in compliance
2742 with section 4.2.1.2 of RFC 3280.
2744 - Fixed a bug introduced by strongswan-2.5.1 which eliminated
2745 not only multiple Quick Modes of a given connection but also
2746 multiple connections between two security gateways.
2752 - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute
2753 installed either by setting auto=route in ipsec.conf or by
2754 a connection put into hold, generates an XFRM_AQUIRE event
2755 for each packet that wants to use the not-yet exisiting
2756 tunnel. Up to now each XFRM_AQUIRE event led to an entry in
2757 the Quick Mode queue, causing multiple IPsec SA to be
2758 established in rapid succession. Starting with strongswan-2.5.1
2759 only a single IPsec SA is established per host-pair connection.
2761 - Right after loading the PKCS#11 module, all smartcard slots are
2762 searched for certificates. The result can be viewed using
2765 ipsec auto --listcards
2767 The certificate objects found in the slots are numbered
2768 starting with #1, #2, etc. This position number can be used to address
2769 certificates (leftcert=%smartcard) and keys (: PIN %smartcard)
2770 in ipsec.conf and ipsec.secrets, respectively:
2772 %smartcard (selects object #1)
2773 %smartcard#1 (selects object #1)
2774 %smartcard#3 (selects object #3)
2776 As an alternative the existing retrieval scheme can be used:
2778 %smartcard:45 (selects object with id=45)
2779 %smartcard0 (selects first object in slot 0)
2780 %smartcard4:45 (selects object in slot 4 with id=45)
2782 - Depending on the settings of CKA_SIGN and CKA_DECRYPT
2783 private key flags either C_Sign() or C_Decrypt() is used
2784 to generate a signature.
2786 - The output buffer length parameter siglen in C_Sign()
2787 is now initialized to the actual size of the output
2788 buffer prior to the function call. This fixes the
2789 CKR_BUFFER_TOO_SMALL error that could occur when using
2790 the OpenSC PKCS#11 module.
2792 - Changed the initialization of the PKCS#11 CK_MECHANISM in
2793 C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }.
2795 - Refactored the RSA public/private key code and transferred it
2796 from keys.c to the new pkcs1.c file as a preparatory step
2797 towards the release of the SCEP client.
2803 - The loading of a PKCS#11 smartcard library module during
2804 runtime does not require OpenSC library functions any more
2805 because the corresponding code has been integrated into
2806 smartcard.c. Also the RSAREF pkcs11 header files have been
2807 included in a newly created pluto/rsaref directory so that
2808 no external include path has to be defined any longer.
2810 - A long-awaited feature has been implemented at last:
2811 The local caching of CRLs fetched via HTTP or LDAP, activated
2812 by the parameter cachecrls=yes in the config setup section
2813 of ipsec.conf. The dynamically fetched CRLs are stored under
2814 a unique file name containing the issuer's subjectKeyID
2815 in /etc/ipsec.d/crls.
2817 - Applied a one-line patch courtesy of Michael Richardson
2818 from the Openswan project which fixes the kernel-oops
2819 in KLIPS when an snmp daemon is running on the same box.
2825 - Eliminated null length CRL distribution point strings.
2827 - Fixed a trust path evaluation bug introduced with 2.4.3
2833 - Improved the joint OCSP / CRL revocation policy.
2834 OCSP responses have precedence over CRL entries.
2836 - Introduced support of CRLv2 reason codes.
2838 - Fixed a bug with key-pad equipped readers which caused
2839 pluto to prompt for the pin via the console when the first
2840 occasion to enter the pin via the key-pad was missed.
2842 - When pluto is built with LDAP_V3 enabled, the library
2843 liblber required by newer versions of openldap is now
2850 - Added the _updown_espmark template which requires all
2851 incoming ESP traffic to be marked with a default mark
2854 - Introduced the pkcs11keepstate parameter in the config setup
2855 section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11
2856 session and login states are kept as long as possible during
2857 the lifetime of pluto. This means that a PIN entry via a key
2858 pad has to be done only once.
2860 - Introduced the pkcs11module parameter in the config setup
2861 section of ipsec.conf which specifies the PKCS#11 module
2862 to be used with smart cards. Example:
2864 pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo
2866 - Added support of smartcard readers equipped with a PIN pad.
2868 - Added patch by Jay Pfeifer which detects when netkey
2869 modules have been statically built into the Linux 2.6 kernel.
2871 - Added two patches by Herbert Xu. The first uses ip xfrm
2872 instead of setkey to flush the IPsec policy database. The
2873 second sets the optional flag in inbound IPComp SAs only.
2875 - Applied Ulrich Weber's patch which fixes an interoperability
2876 problem between native IPsec and KLIPS systems caused by
2877 setting the replay window to 32 instead of 0 for ipcomp.
2883 - Fixed a bug which caused an unwanted Mode Config request
2884 to be initiated in the case where "right" was used to denote
2885 the local side in ipsec.conf and "left" the remote side,
2886 contrary to the recommendation that "right" be remote and
2893 - updated Vendor ID to strongSwan-2.4.0
2895 - updated copyright statement to include David Buechi and
2902 - strongSwan now communicates with attached smartcards and
2903 USB crypto tokens via the standardized PKCS #11 interface.
2904 By default the OpenSC library from www.opensc.org is used
2905 but any other PKCS#11 library could be dynamically linked.
2906 strongSwan's PKCS#11 API was implemented by David Buechi
2907 and Michael Meier, both graduates of the Zurich University
2908 of Applied Sciences in Winterthur, Switzerland.
2910 - When a %trap eroute is triggered by an outgoing IP packet
2911 then the native IPsec stack of the Linux 2.6 kernel [often/
2912 always?] returns an XFRM_ACQUIRE message with an undefined
2913 protocol family field and the connection setup fails.
2914 As a workaround IPv4 (AF_INET) is now assumed.
2916 - the results of the UML test scenarios are now enhanced
2917 with block diagrams of the virtual network topology used
2918 in a particular test.
2924 - fixed IV used to decrypt informational messages.
2925 This bug was introduced with Mode Config functionality.
2927 - fixed NCP Vendor ID.
2929 - undid one of Ulrich Weber's maximum udp size patches
2930 because it caused a segmentation fault with NAT-ed
2933 - added UML scenarios wildcards and attr-cert which
2934 demonstrate the implementation of IPsec policies based
2935 on wildcard parameters contained in Distinguished Names and
2936 on X.509 attribute certificates, respectively.
2942 - Added basic Mode Config functionality
2944 - Added Mathieu Lafon's patch which upgrades the status of
2945 the NAT-Traversal implementation to RFC 3947.
2947 - The _startklips script now also loads the xfrm4_tunnel
2950 - Added Ulrich Weber's netlink replay window size and
2951 maximum udp size patches.
2953 - UML testing now uses the Linux 2.6.10 UML kernel by default.
2959 - Eric Marchionni and Patrik Rayo, both recent graduates from
2960 the Zuercher Hochschule Winterthur in Switzerland, created a
2961 User-Mode-Linux test setup for strongSwan. For more details
2962 please read the INSTALL and README documents in the testing
2965 - Full support of group attributes based on X.509 attribute
2966 certificates. Attribute certificates can be generated
2967 using the openac facility. For more details see
2971 The group attributes can be used in connection definitions
2972 in order to give IPsec access to specific user groups.
2973 This is done with the new parameter left|rightgroups as in
2975 rightgroups="Research, Sales"
2977 giving access to users possessing the group attributes
2978 Research or Sales, only.
2980 - In Quick Mode clients with subnet mask /32 are now
2981 coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should
2982 fix rekeying problems with the SafeNet/SoftRemote and NCP
2983 Secure Entry Clients.
2985 - Changed the defaults of the ikelifetime and keylife parameters
2986 to 3h and 1h, respectively. The maximum allowable values are
2987 now both set to 24 h.
2989 - Suppressed notification wars between two IPsec peers that
2990 could e.g. be triggered by incorrect ISAKMP encryption.
2992 - Public RSA keys can now have identical IDs if either the
2993 issuing CA or the serial number is different. The serial
2994 number of a certificate is now shown by the command
2996 ipsec auto --listpubkeys
3002 - Added Tuomo Soini's sourceip feature which allows a strongSwan
3003 roadwarrior to use a fixed Virtual IP (see README section 2.6)
3004 and reduces the well-known four tunnel case on VPN gateways to
3005 a single tunnel definition (see README section 2.4).
3007 - Fixed a bug occurring with NAT-Traversal enabled when the responder
3008 suddenly turns initiator and the initiator cannot find a matching
3009 connection because of the floated IKE port 4500.
3011 - Removed misleading ipsec verify command from barf.
3013 - Running under the native IP stack, ipsec --version now shows
3014 the Linux kernel version (courtesy to the Openswan project).
3020 - Introduced the ipsec auto --listalgs monitoring command which lists
3021 all currently registered IKE and ESP algorithms.
3023 - Fixed a bug in the ESP algorithm selection occurring when the strict flag
3024 is set and the first proposed transform does not match.
3026 - Fixed another deadlock in the use of the lock_certs_and_keys() mutex,
3027 occurring when a smartcard is present.
3029 - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event.
3031 - Fixed the printing of the notification names (null)
3033 - Applied another of Herbert Xu's Netlink patches.
3039 - Support of Dead Peer Detection. The connection parameter
3041 dpdaction=clear|hold
3043 activates DPD for the given connection.
3045 - The default Opportunistic Encryption (OE) policy groups are not
3046 automatically included anymore. Those wishing to activate OE can include
3047 the policy group with the following statement in ipsec.conf:
3049 include /etc/ipsec.d/examples/oe.conf
3051 The default for [right|left]rsasigkey is now set to %cert.
3053 - strongSwan now has a Vendor ID of its own which can be activated
3054 using the compile option VENDORID
3056 - Applied Herbert Xu's patch which sets the compression algorithm correctly.
3058 - Applied Herbert Xu's patch fixing an ESPINUDP problem
3060 - Applied Herbert Xu's patch setting source/destination port numbers.
3062 - Reapplied one of Herbert Xu's NAT-Traversal patches which got
3063 lost during the migration from SuperFreeS/WAN.
3065 - Fixed a deadlock in the use of the lock_certs_and_keys() mutex.
3067 - Fixed the unsharing of alg parameters when instantiating group
3074 - Thomas Walpuski made me aware of a potential DoS attack via
3075 a PKCS#7-wrapped certificate bundle which could overwrite valid CA
3076 certificates in Pluto's authority certificate store. This vulnerability
3077 was fixed by establishing trust in CA candidate certificates up to a
3078 trusted root CA prior to insertion into Pluto's chained list.
3080 - replaced the --assign option by the -v option in the auto awk script
3081 in order to make it run with mawk under debian/woody.
3087 - Split of the status information between ipsec auto --status (concise)
3088 and ipsec auto --statusall (verbose). Both commands can be used with
3089 an optional connection selector:
3091 ipsec auto --status[all] <connection_name>
3093 - Added the description of X.509 related features to the ipsec_auto(8)
3096 - Hardened the ASN.1 parser in debug mode, especially the printing
3097 of malformed distinguished names.
3099 - The size of an RSA public key received in a certificate is now restricted to
3101 512 bits <= modulus length <= 8192 bits.
3103 - Fixed the debug mode enumeration.
3109 - Fixed another PKCS#7 vulnerability which could lead to an
3110 endless loop while following the X.509 trust chain.
3116 - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski
3117 that accepted end certificates having identical issuer and subject
3118 distinguished names in a multi-tier X.509 trust chain.
3124 - Removed all remaining references to ipsec_netlink.h in KLIPS.
3130 - The new "ca" section allows to define the following parameters:
3133 cacert=koolCA.pem # cacert of kool CA
3134 ocspuri=http://ocsp.kool.net:8001 # ocsp server
3135 ldapserver=ldap.kool.net # default ldap server
3136 crluri=http://www.kool.net/kool.crl # crl distribution point
3137 crluri2="ldap:///O=Kool, C= .." # crl distribution point #2
3138 auto=add # add, ignore
3140 The ca definitions can be monitored via the command
3142 ipsec auto --listcainfos
3144 - Fixed cosmetic corruption of /proc filesystem by integrating
3145 D. Hugh Redelmeier's freeswan-2.06 kernel fixes.
3151 - Added support for the 818043 NAT-Traversal update of Microsoft's
3152 Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode.
3154 - A symbolic link to libcrypto is now added in the kernel sources
3155 during kernel compilation
3157 - Fixed a couple of 64 bit issues (mostly casts to int).
3158 Thanks to Ken Bantoft who checked my sources on a 64 bit platform.
3160 - Replaced s[n]printf() statements in the kernel by ipsec_snprintf().
3161 Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro
3162 of the FreeS/WAN team who solved this problem with the 2.4.25 kernel.
3168 - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName
3169 certificate extension which contains no generalName item) can cause
3170 a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has
3171 been hardened to make it more robust against malformed ASN.1 objects.
3173 - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native
3174 Linux 2.6 IPsec stack.
3180 - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12
projects / strongswan.git / blob