4 - The pki tool accepts a xmppAddr otherName as a subjectAlternativeName using
5 the syntax --san xmppaddr:<jid>.
7 - Implementation of RFC 8412 "Software Inventory Message and Attributes (SWIMA)
10 - Added support for fuzzing the PA-TNC (RFC 5792) and PB-TNC (RFC 5793) NEA
11 protocols on Google's OSS-Fuzz infrastructure.
13 - Support for version 2 of Intel's TPM2-TSS TGC Software Stack.
19 - Fixed a DoS vulnerability in the IKEv2 key derivation if the openssl plugin is
20 used in FIPS mode and HMAC-MD5 is negotiated as PRF.
21 This vulnerability has been registered as CVE-2018-10811.
23 - Fixed a vulnerability in the stroke plugin, which did not check the received
24 length before reading a message from the socket. Unless a group is configured,
25 root privileges are required to access that socket, so in the default
26 configuration this shouldn't be an issue.
27 This vulnerability has been registered as CVE-2018-5388.
29 ⁻ CRLs that are not yet valid are now ignored to avoid problems in scenarios
30 where expired certificates are removed from CRLs and the clock on the host
31 doing the revocation check is trailing behind that of the host issuing CRLs.
33 - The issuer of fetched CRLs is now compared to the issuer of the checked
36 - CRL validation results other than revocation (e.g. a skipped check because
37 the CRL couldn't be fetched) are now stored also for intermediate CA
38 certificates and not only for end-entity certificates, so a strict CRL policy
39 can be enforced in such cases.
41 - In compliance with RFC 4945, section 5.1.3.2, certificates used for IKE must
42 now either not contain a keyUsage extension (like the ones generated by pki)
43 or have at least one of the digitalSignature or nonRepudiation bits set.
45 - New options for vici/swanctl allow forcing the local termination of an IKE_SA.
46 This might be useful in situations where it's known the other end is not
47 reachable anymore, or that it already removed the IKE_SA, so retransmitting a
48 DELETE and waiting for a response would be pointless. Waiting only a certain
49 amount of time for a response before destroying the IKE_SA is also possible
50 by additionally specifying a timeout.
52 - When removing routes, the kernel-netlink plugin now checks if it tracks other
53 routes for the same destination and replaces the installed route instead of
54 just removing it. Same during installation, where existing routes previously
55 weren't replaced. This should allow using traps with virtual IPs on Linux.
57 - The dhcp plugin only sends the client identifier option if identity_lease is
58 enabled. It can also send identities of up to 255 bytes length, instead of
59 the previous 64 bytes. If a server address is configured, DHCP requests are
60 now sent from port 67 instead of 68 to avoid ICMP port unreachables.
62 - Roam events are now completely ignored for IKEv1 SAs.
64 - ChaCha20/Poly1305 is now correctly proposed without key length. For
65 compatibility with older releases the chacha20poly1305compat keyword may be
66 included in proposals to also propose the algorithm with a key length.
68 - Configuration of hardware offload of IPsec SAs is now more flexible and allows
69 a new mode, which automatically uses it if the kernel and device support it.
71 - SHA-2 based PRFs are supported in PKCS#8 files as generated by OpenSSL 1.1.
73 - The pki --verify tool may load CA certificates and CRLs from directories.
75 - Fixed an issue with DNS servers passed to NetworkManager in charon-nm.
81 - Fixed a DoS vulnerability in the parser for PKCS#1 RSASSA-PSS signatures that
82 was caused by insufficient input validation. One of the configurable
83 parameters in algorithm identifier structures for RSASSA-PSS signatures is the
84 mask generation function (MGF). Only MGF1 is currently specified for this
85 purpose. However, this in turn takes itself a parameter that specifies the
86 underlying hash function. strongSwan's parser did not correctly handle the
87 case of this parameter being absent, causing an undefined data read.
88 This vulnerability has been registered as CVE-2018-6459.
90 - The previously negotiated DH group is reused when rekeying an SA, instead of
91 using the first group in the configured proposals, which avoids an additional
92 exchange if the peer selected a different group via INVALID_KE_PAYLOAD when
93 the SA was created initially.
94 The selected DH group is also moved to the front of all sent proposals that
95 contain it and all proposals that don't are moved to the back in order to
96 convey the preference for this group to the peer.
98 - Handling of MOBIKE task queuing has been improved. In particular, the response
99 to an address update is not ignored anymore if only an address list update or
102 - The fallback drop policies installed to avoid traffic leaks when replacing
103 addresses in installed policies are now replaced by temporary drop policies,
104 which also prevent acquires because we currently delete and reinstall IPsec
105 SAs to update their addresses.
107 - Access X.509 certificates held in non-volatile storage of a TPM 2.0
108 referenced via the NV index.
110 - Adding the --keyid parameter to pki --print allows to print private keys
111 or certificates stored in a smartcard or a TPM 2.0.
113 - Fixed proposal selection if a peer incorrectly sends DH groups in the ESP
114 proposals during IKE_AUTH and also if a DH group is configured in the local
115 ESP proposal and charon.prefer_configured_proposals is disabled.
117 - MSKs received via RADIUS are now padded to 64 bytes to avoid compatibility
118 issues with EAP-MSCHAPv2 and PRFs that have a block size < 64 bytes (e.g.
121 - The tpm_extendpcr command line tool extends a digest into a TPM PCR.
123 - Ported the NetworkManager backend from the deprecated libnm-glib to libnm.
125 - The save-keys debugging/development plugin saves IKE and/or ESP keys to files
126 compatible with Wireshark.
132 - In compliance with RFCs 8221 and 8247 several algorithms were removed from the
133 default ESP/AH and IKEv2 proposals, respectively (3DES, Blowfish and MD5 from
134 ESP/AH, MD5 and MODP-1024 from IKEv2). These algorithms may still be used in
137 - Added support for RSASSA-PSS signatures. For backwards compatibility they are
138 not used automatically by default, enable charon.rsa_pss to change that. To
139 explicitly use or require such signatures with IKEv2 signature authentication
140 (RFC 7427), regardless of whether that option is enabled, use ike:rsa/pss...
141 authentication constraints.
143 - The pki tool can optionally sign certificates/CRLs with RSASSA-PSS via the
144 `--rsa-padding pss` option.
146 - The sec-updater tool checks for security updates in dpkg-based repositories
147 (e.g. Debian/Ubuntu) and sets the security flags in the IMV policy database
148 accordingly. Additionally for each new package version a SWID tag for the
149 given OS and HW architecture is created and stored in the database.
150 Using the sec-updater.sh script template the lookup can be automated
151 (e.g. via an hourly cron job).
153 - The introduction of file versions in the IMV database scheme broke file
154 reference hash measurements. This has been fixed by creating generic product
155 versions having an empty package name.
157 - A new timeout option for the systime-fix plugin stops periodic system time
158 checks after a while and enforces a certificate verification, closing or
159 reauthenticating all SAs with invalid certificates.
161 - The IKE event counters, previously only available via ipsec listcounters, may
162 now be queried/reset via vici and the new swanctl --counters command. They are
163 provided by the new optional counters plugin.
165 - Class attributes received in RADIUS Access-Accept messages may optionally be
166 added to RADIUS accounting messages.
168 - Inbound marks may optionally be installed on the SA again (was removed with
169 5.5.2) by enabling the mark_in_sa option in swanctl.conf.
175 - Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
176 input validation when verifying RSA signatures, which requires decryption
177 with the operation m^e mod n, where m is the signature, and e and n are the
178 exponent and modulus of the public key. The value m is an integer between
179 0 and n-1, however, the gmp plugin did not verify this. So if m equals n the
180 calculation results in 0, in which case mpz_export() returns NULL. This
181 result wasn't handled properly causing a null-pointer dereference.
182 This vulnerability has been registered as CVE-2017-11185.
184 - New SWIMA IMC/IMV pair implements the "draft-ietf-sacm-nea-swima-patnc"
185 Internet Draft and has been demonstrated at the IETF 99 Prague Hackathon.
187 - The IMV database template has been adapted to achieve full compliance
188 with the ISO 19770-2:2015 SWID tag standard.
190 - The sw-collector tool extracts software events from apt history logs
191 and stores them in an SQLite database to be used by the SWIMA IMC.
192 The tool can also generate SWID tags both for installed and removed
195 - The pt-tls-client can attach and use TPM 2.0 protected private keys
196 via the --keyid parameter.
198 - libtpmtss supports Intel's TSS2 Architecture Broker and Resource
199 Manager interface (tcti-tabrmd).
201 - The new eap-aka-3gpp plugin implements the 3GPP MILENAGE algorithms
202 in software. K (optionally concatenated with OPc) may be configured as
205 - CHILD_SA rekeying was fixed in charon-tkm and was slightly changed: The
206 switch to the new outbound IPsec SA now happens via SPI on the outbound
207 policy on Linux, and in case of lost rekey collisions no outbound SA/policy
208 is temporarily installed for the redundant CHILD_SA.
210 - The new %unique-dir value for mark* settings allocates separate unique marks
211 for each CHILD_SA direction (in/out).
217 - Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
218 input validation when verifying RSA signatures. More specifically,
219 mpz_powm_sec() has two requirements regarding the passed exponent and modulus
220 that the plugin did not enforce, if these are not met the calculation will
221 result in a floating point exception that crashes the whole process.
222 This vulnerability has been registered as CVE-2017-9022.
224 - Fixed a DoS vulnerability in the x509 plugin that was caused because the ASN.1
225 parser didn't handle ASN.1 CHOICE types properly, which could result in an
226 infinite loop when parsing X.509 extensions that use such types.
227 This vulnerability has been registered as CVE-2017-9023.
229 - The behavior during IKEv2 CHILD_SA rekeying has been changed in order to avoid
230 traffic loss. The responder now only installs the new inbound SA and delays
231 installing the outbound SA until it receives the DELETE for the replaced
232 CHILD_SA. Similarly, the inbound SA of the replaced CHILD_SA is not removed
233 for a configurable amount of seconds (charon.delete_rekeyed_delay) after the
234 DELETE has been processed to reduce the chance of dropping delayed packets.
236 - The code base has been ported to Apple's ARM64 iOS platform, whose calling
237 conventions for variadic and regular functions are different. This means
238 assigning non-variadic functions to variadic function pointers does not work.
239 To avoid this issue the enumerator_t interface has been changed and the
240 signatures of the callback functions for enumerator_create_filter(), and the
241 invoke_function() and find_first() methods on linked_list_t have been changed.
242 The return type of find_first() also changed from status_t to bool.
244 - Added support for fuzzing the certificate parser provided by the default
245 plugins (x509, pem, gmp etc.) on Google's OSS-Fuzz infrastructure. Several
246 issues found while fuzzing these plugins were fixed.
248 - Two new options have been added to charon's retransmission settings:
249 retransmit_limit and retransmit_jitter. The former adds an upper limit to the
250 calculated retransmission timeout, the latter randomly reduces it.
252 - A bug in swanctl's --load-creds command was fixed that caused unencrypted
253 private keys to get unloaded if the command was called multiple times. The
254 load-key VICI command now returns the key ID of the loaded key on success.
256 - The credential manager now enumerates local credential sets before global
257 ones. This means certificates supplied by the peer will now be preferred over
258 certificates with the same identity that may be locally stored (e.g. in the
261 - Added support for hardware offload of IPsec SAs as introduced by Linux 4.11
262 for hardware that supports this.
264 - When building the libraries monolithically and statically the plugin
265 constructors are now hard-coded in each library so the plugin code is not
266 removed by the linker because it thinks none of their symbols are ever
269 - The pki tool loads the curve25519 plugin by default.
275 - Support of Diffie-Hellman group 31 using Curve25519 for IKE as defined
278 - Support of Ed25519 digital signature algorithm for IKEv2 as defined by
279 draft-ietf-ipsecme-eddsa. Ed25519-based public key pairs, X.509 certificates
280 and CRLs can be generated and printed by the pki tool.
282 - The new "tpm" libtpmtss plugin allows to use persistent private RSA and ECDSA
283 keys bound to a TPM 2.0 for both IKE and TLS authentication. Using the
284 TPM 2.0 object handle as keyid parameter, the pki --pub tool can extract
285 the public key from the TPM thereby replacing the aikpub2 tool. In a similar
286 fashion pki --req can generate a PKCS#10 certificate request signed with
289 - The pki tool gained support for generating certificates with the RFC 3779
290 addrblock extension. The charon addrblock plugin now dynamically narrows
291 traffic selectors based on the certificate addrblocks instead of rejecting
292 non-matching selectors completely. This allows generic connections, where
293 the allowed selectors are defined by the used certificates only.
295 - In-place update of cached base and delta CRLs does not leave dozens
296 of stale copies in cache memory.
298 - Several new features for the VICI interface and the swanctl utility: Querying
299 specific pools, enumerating and unloading keys and shared secrets, loading
300 keys and certificates from PKCS#11 tokens, the ability to initiate, install
301 and uninstall connections and policies by their exact name (if multiple child
302 sections in different connections share the same name), a command to initiate
303 the rekeying of IKE and IPsec SAs, support for settings previously only
304 supported by the old config files (plain pubkeys, dscp, certificate policies,
305 IPv6 Transport Proxy Mode, NT Hash secrets, mediation extension).
307 Important: Due to issues with VICI bindings that map sub-sections to
308 dictionaries the CHILD_SA sections returned via list-sas now have a unique
309 name, the original name of a CHILD_SA is returned in the "name" key of its
316 - The newhope plugin implements the post-quantum NewHope key exchange algorithm
317 proposed in their 2015 paper by Erdem Alkim, Léo Ducas, Thomas Pöppelmann and
320 - The libstrongswan crypto factory now offers the registration of Extended
321 Output Functions (XOFs). Currently supported XOFs are SHAKE128 and SHAKE256
322 implemented by the sha3 plugin, ChaCHa20 implemented by the chapoly plugin
323 and the more traditional MGF1 Mask Generation Functions based on the SHA-1,
324 SHA-256 and SHA-512 hash algorithms implemented by the new mgf1 plugin.
326 - The pki tool, with help of the pkcs1 or openssl plugins, can parse private
327 keys in any of the supported formats without having to know the exact type.
328 So instead of having to specify rsa or ecdsa explicitly the keyword priv may
329 be used to indicate a private key of any type. Similarly, swanctl can load
330 any type of private key from the swanctl/private directory.
332 - The pki tool can handle RSASSA-PKCS1v1.5-with-SHA-3 signatures using the
333 sha3 and gmp plugins.
335 - The VICI flush-certs command flushes certificates from the volatile
336 certificate cache. Optionally the type of the certificates to be
337 flushed (e.g. type = x509_crl) can be specified.
339 - Setting cache_crls = yes in strongswan.conf the vici plugin saves regular,
340 base and delta CRLs to disk.
342 - IKE fragmentation is now enabled by default with the default fragment size
343 set to 1280 bytes for both IP address families.
345 - libtpmtss: In the TSS2 API the function TeardownSocketTcti() was replaced by
346 tss2_tcti_finalize().
352 - The new libtpmtss library offers support for both TPM 1.2 and TPM 2.0
353 Trusted Platform Modules. This allows the Attestation IMC/IMV pair to
354 do TPM 2.0 based attestation.
356 - The behavior during IKEv2 exchange collisions has been improved/fixed in
357 several corner cases and support for TEMPORARY_FAILURE and CHILD_SA_NOT_FOUND
358 notifies, as defined by RFC 7296, has been added.
360 - IPsec policy priorities can be set manually (e.g. for high-priority drop
361 policies) and outbound policies may be restricted to a network interface.
363 - The scheme for the automatically calculated default priorities has been
364 changed and now also considers port masks, which were added with 5.4.0.
366 - FWD policies are now installed in both directions in regards to the traffic
367 selectors. Because such "outbound" FWD policies could conflict with "inbound"
368 FWD policies of other SAs they are installed with a lower priority and don't
369 have a reqid set, which allows kernel plugins to distinguish between the two
370 and prefer those with a reqid.
372 - For outbound IPsec SAs no replay window is configured anymore.
374 - Enhanced the functionality of the swanctl --list-conns command by listing
375 IKE_SA and CHILD_SA reauthentication and rekeying settings, and EAP/XAuth
376 identities and EAP types.
378 - DNS servers installed by the resolve plugin are now refcounted, which should
379 fix its use with make-before-break reauthentication. Any output written to
380 stderr/stdout by resolvconf is now logged.
382 - The methods in the kernel interfaces have been changed to take structs instead
383 of long lists of arguments. Similarly the constructors for peer_cfg_t and
384 child_cfg_t now take structs.
390 - Support for IKEv2 redirection (RFC 5685) has been added. Plugins may
391 implement the redirect_provider_t interface to decide if and when to redirect
392 connecting clients. It is also possible to redirect established IKE_SAs based
393 on different selectors via VICI/swanctl. Unless disabled in strongswan.conf
394 the charon daemon will follow redirect requests received from servers.
396 - The ike: prefix enables the explicit configuration of signature scheme
397 constraints against IKEv2 authentication in rightauth, which allows the use
398 of different signature schemes for trustchain verification and authentication.
400 - The initiator of an IKEv2 make-before-break reauthentication now suspends
401 online certificate revocation checks (OCSP, CRLs) until the new IKE_SA and all
402 CHILD_SAs are established. This is required if the checks are done over the
403 CHILD_SA established with the new IKE_SA. This is not possible until the
404 initiator installs this SA and that only happens after the authentication is
405 completed successfully. So we suspend the checks during the reauthentication
406 and do them afterwards, if they fail the IKE_SA is closed. This change has no
407 effect on the behavior during the authentication of the initial IKE_SA.
409 - For the vici plugin a Vici:Session Perl CPAN module has been added to allow
410 Perl applications to control and/or monitor the IKE daemon using the VICI
411 interface, similar to the existing Python egg or Ruby gem.
413 - Traffic selectors with port ranges can now be configured in the Linux kernel:
414 e.g. remote_ts = 10.1.0.0/16[tcp/20-23] local_ts = dynamic[tcp/32768-65535].
415 The port range must map to a port mask, though since the kernel does not
416 support arbitrary ranges.
418 - The vici plugin allows the configuration of IPv4 and IPv6 address ranges
419 in local and remote traffic selectors. Since both the Linux kernel and
420 iptables cannot handle arbitrary ranges, address ranges are mapped to the next
421 larger CIDR subnet by the kernel-netlink and updown plugins, respectively.
423 - Implemented IKEv1 IPv4/IPv6 address subnet and range identities that can be
424 used as owners of shared secrets.
430 - Properly handle potential EINTR errors in sigwaitinfo(2) calls that replaced
431 sigwait(3) calls with 5.3.4.
433 - RADIUS retransmission timeouts are now configurable, courtesy of Thom Troy.
439 - Fixed an authentication bypass vulnerability in the eap-mschapv2 plugin that
440 was caused by insufficient verification of the internal state when handling
441 MSCHAPv2 Success messages received by the client.
442 This vulnerability has been registered as CVE-2015-8023.
444 - The sha3 plugin implements the SHA3 Keccak-F1600 hash algorithm family.
445 Within the strongSwan framework SHA3 is currently used for BLISS signatures
446 only because the OIDs for other signature algorithms haven't been defined
447 yet. Also the use of SHA3 for IKEv2 has not been standardized yet.
453 - Added support for the ChaCha20/Poly1305 AEAD cipher specified in RFC 7539 and
454 RFC 7634 using the chacha20poly1305 ike/esp proposal keyword. The new chapoly
455 plugin implements the cipher, if possible SSE-accelerated on x86/x64
456 architectures. It is usable both in IKEv2 and the strongSwan libipsec ESP
457 backend. On Linux 4.2 or newer the kernel-netlink plugin can configure the
460 - The vici interface now supports the configuration of auxiliary certification
461 authority information as CRL and OCSP URIs.
463 - In the bliss plugin the c_indices derivation using a SHA-512 based random
464 oracle has been fixed, generalized and standardized by employing the MGF1 mask
465 generation function with SHA-512. As a consequence BLISS signatures unsing the
466 improved oracle are not compatible with the earlier implementation.
468 - Support for auto=route with right=%any for transport mode connections has
469 been added (the ikev2/trap-any scenario provides examples).
471 - The starter daemon does not flush IPsec policies and SAs anymore when it is
472 stopped. Already existing duplicate policies are now overwritten by the IKE
473 daemon when it installs its policies.
475 - Init limits (like charon.init_limit_half_open) can now optionally be enforced
476 when initiating SAs via VICI. For this, IKE_SAs initiated by the daemon are
477 now also counted as half-open SAs, which, as a side-effect, fixes the status
478 output while connecting (e.g. in ipsec status).
480 - Symmetric configuration of EAP methods in left|rightauth is now possible when
481 mutual EAP-only authentication is used (previously, the client had to
482 configure rightauth=eap or rightauth=any, which prevented it from using this
483 same config as responder).
485 - The initiator flag in the IKEv2 header is compared again (wasn't the case
486 since 5.0.0) and packets that have the flag set incorrectly are again ignored.
488 - Implemented a demo Hardcopy Device IMC/IMV pair based on the "Hardcopy
489 Device Health Assessment Trusted Network Connect Binding" (HCD-TNC)
490 document drafted by the IEEE Printer Working Group (PWG).
492 - Fixed IF-M segmentation which failed in the presence of multiple small
493 attributes in front of a huge attribute to be segmented.
499 - Fixed a vulnerability that allowed rogue servers with a valid certificate
500 accepted by the client to trick it into disclosing its username and even
501 password (if the client accepts EAP-GTC). This was caused because constraints
502 against the responder's authentication were enforced too late.
503 This vulnerability has been registered as CVE-2015-4171.
509 - Fixed a denial-of-service and potential remote code execution vulnerability
510 triggered by IKEv1/IKEv2 messages that contain payloads for the respective
511 other IKE version. Such payload are treated specially since 5.2.2 but because
512 they were still identified by their original payload type they were used as
513 such in some places causing invalid function pointer dereferences.
514 The vulnerability has been registered as CVE-2015-3991.
516 - The new aesni plugin provides CBC, CTR, XCBC, CMAC, CCM and GCM crypto
517 primitives for AES-128/192/256. The plugin requires AES-NI and PCLMULQDQ
518 instructions and works on both x86 and x64 architectures. It provides
519 superior crypto performance in userland without any external libraries.
525 - Added support for IKEv2 make-before-break reauthentication. By using a global
526 CHILD_SA reqid allocation mechanism, charon supports overlapping CHILD_SAs.
527 This allows the use of make-before-break instead of the previously supported
528 break-before-make reauthentication, avoiding connectivity gaps during that
529 procedure. As the new mechanism may fail with peers not supporting it (such
530 as any previous strongSwan release) it must be explicitly enabled using
531 the charon.make_before_break strongswan.conf option.
533 - Support for "Signature Authentication in IKEv2" (RFC 7427) has been added.
534 This allows the use of stronger hash algorithms for public key authentication.
535 By default, signature schemes are chosen based on the strength of the
536 signature key, but specific hash algorithms may be configured in leftauth.
538 - Key types and hash algorithms specified in rightauth are now also checked
539 against IKEv2 signature schemes. If such constraints are used for certificate
540 chain validation in existing configurations, in particular with peers that
541 don't support RFC 7427, it may be necessary to disable this feature with the
542 charon.signature_authentication_constraints setting, because the signature
543 scheme used in classic IKEv2 public key authentication may not be strong
546 - The new connmark plugin allows a host to bind conntrack flows to a specific
547 CHILD_SA by applying and restoring the SA mark to conntrack entries. This
548 allows a peer to handle multiple transport mode connections coming over the
549 same NAT device for client-initiated flows. A common use case is to protect
550 L2TP/IPsec, as supported by some systems.
552 - The forecast plugin can forward broadcast and multicast messages between
553 connected clients and a LAN. For CHILD_SA using unique marks, it sets up
554 the required Netfilter rules and uses a multicast/broadcast listener that
555 forwards such messages to all connected clients. This plugin is designed for
556 Windows 7 IKEv2 clients, which announces its services over the tunnel if the
557 negotiated IPsec policy allows it.
559 - For the vici plugin a Python Egg has been added to allow Python applications
560 to control or monitor the IKE daemon using the VICI interface, similar to the
561 existing ruby gem. The Python library has been contributed by Björn Schuberg.
563 - EAP server methods now can fulfill public key constraints, such as rightcert
564 or rightca. Additionally, public key and signature constraints can be
565 specified for EAP methods in the rightauth keyword. Currently the EAP-TLS and
566 EAP-TTLS methods provide verification details to constraints checking.
568 - Upgrade of the BLISS post-quantum signature algorithm to the improved BLISS-B
569 variant. Can be used in conjunction with the SHA256, SHA384 and SHA512 hash
570 algorithms with SHA512 being the default.
572 - The IF-IMV 1.4 interface now makes the IP address of the TNC access requestor
573 as seen by the TNC server available to all IMVs. This information can be
574 forwarded to policy enforcement points (e.g. firewalls or routers).
576 - The new mutual tnccs-20 plugin parameter activates mutual TNC measurements
577 in PB-TNC half-duplex mode between two endpoints over either a PT-EAP or
578 PT-TLS transport medium.
584 - Fixed a denial-of-service vulnerability triggered by an IKEv2 Key Exchange
585 payload that contains the Diffie-Hellman group 1025. This identifier was
586 used internally for DH groups with custom generator and prime. Because
587 these arguments are missing when creating DH objects based on the KE payload
588 an invalid pointer dereference occurred. This allowed an attacker to crash
589 the IKE daemon with a single IKE_SA_INIT message containing such a KE
590 payload. The vulnerability has been registered as CVE-2014-9221.
592 - The left/rightid options in ipsec.conf, or any other identity in strongSwan,
593 now accept prefixes to enforce an explicit type, such as email: or fqdn:.
594 Note that no conversion is done for the remaining string, refer to
595 ipsec.conf(5) for details.
597 - The post-quantum Bimodal Lattice Signature Scheme (BLISS) can be used as
598 an IKEv2 public key authentication method. The pki tool offers full support
599 for the generation of BLISS key pairs and certificates.
601 - Fixed mapping of integrity algorithms negotiated for AH via IKEv1. This could
602 cause interoperability issues when connecting to older versions of charon.
608 - The new charon-systemd IKE daemon implements an IKE daemon tailored for use
609 with systemd. It avoids the dependency on ipsec starter and uses swanctl
610 as configuration backend, building a simple and lightweight solution. It
611 supports native systemd journal logging.
613 - Support for IKEv2 fragmentation as per RFC 7383 has been added. Like IKEv1
614 fragmentation it can be enabled by setting fragmentation=yes in ipsec.conf.
616 - Support of the TCG TNC IF-M Attribute Segmentation specification proposal.
617 All attributes can be segmented. Additionally TCG/SWID Tag, TCG/SWID Tag ID
618 and IETF/Installed Packages attributes can be processed incrementally on a
621 - The new ext-auth plugin calls an external script to implement custom IKE_SA
622 authorization logic, courtesy of Vyronas Tsingaras.
624 - For the vici plugin a ruby gem has been added to allow ruby applications
625 to control or monitor the IKE daemon. The vici documentation has been updated
626 to include a description of the available operations and some simple examples
627 using both the libvici C interface and the ruby gem.
633 - strongSwan has been ported to the Windows platform. Using a MinGW toolchain,
634 many parts of the strongSwan codebase run natively on Windows 7 / 2008 R2
635 and newer releases. charon-svc implements a Windows IKE service based on
636 libcharon, the kernel-iph and kernel-wfp plugins act as networking and IPsec
637 backend on the Windows platform. socket-win provides a native IKE socket
638 implementation, while winhttp fetches CRL and OCSP information using the
641 - The new vici plugin provides a Versatile IKE Configuration Interface for
642 charon. Using the stable IPC interface, external applications can configure,
643 control and monitor the IKE daemon. Instead of scripting the ipsec tool
644 and generating ipsec.conf, third party applications can use the new interface
645 for more control and better reliability.
647 - Built upon the libvici client library, swanctl implements the first user of
648 the VICI interface. Together with a swanctl.conf configuration file,
649 connections can be defined, loaded and managed. swanctl provides a portable,
650 complete IKE configuration and control interface for the command line.
651 The first six swanctl example scenarios have been added.
653 - The SWID IMV implements a JSON-based REST API which allows the exchange
654 of SWID tags and Software IDs with the strongTNC policy manager.
656 - The SWID IMC can extract all installed packages from the dpkg (Debian,
657 Ubuntu, Linux Mint etc.), rpm (Fedora, RedHat, OpenSUSE, etc.), or
658 pacman (Arch Linux, Manjaro, etc.) package managers, respectively, using the
659 swidGenerator (https://github.com/strongswan/swidGenerator) which generates
660 SWID tags according to the new ISO/IEC 19770-2:2014 standard.
662 - All IMVs now share the access requestor ID, device ID and product info
663 of an access requestor via a common imv_session object.
665 - The Attestation IMC/IMV pair supports the IMA-NG measurement format
666 introduced with the Linux 3.13 kernel.
668 - The aikgen tool generates an Attestation Identity Key bound to a TPM.
670 - Implemented the PT-EAP transport protocol (RFC 7171) for Trusted Network
673 - The ipsec.conf replay_window option defines connection specific IPsec replay
674 windows. Original patch courtesy of Zheng Zhong and Christophe Gouault from
681 - Fixed an authentication bypass vulnerability triggered by rekeying an
682 unestablished IKEv2 SA while it gets actively initiated. This allowed an
683 attacker to trick a peer's IKE_SA state to established, without the need to
684 provide any valid authentication credentials. The vulnerability has been
685 registered as CVE-2014-2338.
687 - The acert plugin evaluates X.509 Attribute Certificates. Group membership
688 information encoded as strings can be used to fulfill authorization checks
689 defined with the rightgroups option. Attribute Certificates can be loaded
690 locally or get exchanged in IKEv2 certificate payloads.
692 - The pki command gained support to generate X.509 Attribute Certificates
693 using the --acert subcommand, while the --print command supports the ac type.
694 The openac utility has been removed in favor of the new pki functionality.
696 - The libtls TLS 1.2 implementation as used by EAP-(T)TLS and other protocols
697 has been extended by AEAD mode support, currently limited to AES-GCM.
703 - A new default configuration file layout is introduced. The new default
704 strongswan.conf file mainly includes config snippets from the strongswan.d
705 and strongswan.d/charon directories (the latter containing snippets for all
706 plugins). The snippets, with commented defaults, are automatically
707 generated and installed, if they don't exist yet. They are also installed
708 in $prefix/share/strongswan/templates so existing files can be compared to
709 the current defaults.
711 - As an alternative to the non-extensible charon.load setting, the plugins
712 to load in charon (and optionally other applications) can now be determined
713 via the charon.plugins.<name>.load setting for each plugin (enabled in the
714 new default strongswan.conf file via the charon.load_modular option).
715 The load setting optionally takes a numeric priority value that allows
716 reordering the plugins (otherwise the default plugin order is preserved).
718 - All strongswan.conf settings that were formerly defined in library specific
719 "global" sections are now application specific (e.g. settings for plugins in
720 libstrongswan.plugins can now be set only for charon in charon.plugins).
721 The old options are still supported, which now allows to define defaults for
722 all applications in the libstrongswan section.
724 - The ntru libstrongswan plugin supports NTRUEncrypt as a post-quantum
725 computer IKE key exchange mechanism. The implementation is based on the
726 ntru-crypto library from the NTRUOpenSourceProject. The supported security
727 strengths are ntru112, ntru128, ntru192, and ntru256. Since the private DH
728 group IDs 1030..1033 have been assigned, the strongSwan Vendor ID must be
729 sent (charon.send_vendor_id = yes) in order to use NTRU.
731 - Defined a TPMRA remote attestation workitem and added support for it to the
734 - Compatibility issues between IPComp (compress=yes) and leftfirewall=yes as
735 well as multiple subnets in left|rightsubnet have been fixed.
737 - When enabling its "session" strongswan.conf option, the xauth-pam plugin opens
738 and closes a PAM session for each established IKE_SA. Patch courtesy of
741 - The strongSwan unit testing framework has been rewritten without the "check"
742 dependency for improved flexibility and portability. It now properly supports
743 multi-threaded and memory leak testing and brings a bunch of new test cases.
749 - Fixed a denial-of-service vulnerability and potential authorization bypass
750 triggered by a crafted ID_DER_ASN1_DN ID payload. The cause is an insufficient
751 length check when comparing such identities. The vulnerability has been
752 registered as CVE-2013-6075.
754 - Fixed a denial-of-service vulnerability triggered by a crafted IKEv1
755 fragmentation payload. The cause is a NULL pointer dereference. The
756 vulnerability has been registered as CVE-2013-6076.
758 - The lean stand-alone pt-tls-client can set up a RFC 6876 PT-TLS session
759 with a strongSwan policy enforcement point which uses the tnc-pdp charon
762 - The new TCG TNC SWID IMC/IMV pair supports targeted SWID requests for either
763 full SWID Tag or concise SWID Tag ID inventories.
765 - The XAuth backend in eap-radius now supports multiple XAuth exchanges for
766 different credential types and display messages. All user input gets
767 concatenated and verified with a single User-Password RADIUS attribute on
768 the AAA. With an AAA supporting it, one for example can implement
769 Password+Token authentication with proper dialogs on iOS and OS X clients.
771 - charon supports IKEv1 Mode Config exchange in push mode. The ipsec.conf
772 modeconfig=push option enables it for both client and server, the same way
775 - Using the "ah" ipsec.conf keyword on both IKEv1 and IKEv2 connections,
776 charon can negotiate and install Security Associations integrity-protected by
777 the Authentication Header protocol. Supported are plain AH(+IPComp) SAs only,
778 but not the deprecated RFC2401 style ESP+AH bundles.
780 - The generation of initialization vectors for IKE and ESP (when using libipsec)
781 is now modularized and IVs for e.g. AES-GCM are now correctly allocated
782 sequentially, while other algorithms like AES-CBC still use random IVs.
784 - The left and right options in ipsec.conf can take multiple address ranges
785 and subnets. This allows connection matching against a larger set of
786 addresses, for example to use a different connection for clients connecting
787 from a internal network.
789 - For all those who have a queasy feeling about the NIST elliptic curve set,
790 the Brainpool curves introduced for use with IKE by RFC 6932 might be a
791 more trustworthy alternative.
793 - The kernel-libipsec userland IPsec backend now supports usage statistics,
794 volume based rekeying and accepts ESPv3 style TFC padded packets.
796 - With two new strongswan.conf options fwmarks can be used to implement
797 host-to-host tunnels with kernel-libipsec.
799 - load-tester supports transport mode connections and more complex traffic
800 selectors, including such using unique ports for each tunnel.
802 - The new dnscert plugin provides support for authentication via CERT RRs that
803 are protected via DNSSEC. The plugin was created by Ruslan N. Marchenko.
805 - The eap-radius plugin supports forwarding of several Cisco Unity specific
806 RADIUS attributes in corresponding configuration payloads.
808 - Database transactions are now abstracted and implemented by the two backends.
809 If you use MySQL make sure all tables use the InnoDB engine.
811 - libstrongswan now can provide an experimental custom implementation of the
812 printf family functions based on klibc if neither Vstr nor glibc style printf
813 hooks are available. This can avoid the Vstr dependency on some systems at
814 the cost of slower and less complete printf functions.
820 - Fixed a denial-of-service vulnerability triggered by specific XAuth usernames
821 and EAP identities (since 5.0.3), and PEM files (since 4.1.11). The crash
822 was caused by insufficient error handling in the is_asn1() function.
823 The vulnerability has been registered as CVE-2013-5018.
825 - The new charon-cmd command line IKE client can establish road warrior
826 connections using IKEv1 or IKEv2 with different authentication profiles.
827 It does not depend on any configuration files and can be configured using a
828 few simple command line options.
830 - The kernel-pfroute networking backend has been greatly improved. It now
831 can install virtual IPs on TUN devices on OS X and FreeBSD, allowing these
832 systems to act as a client in common road warrior scenarios.
834 - The new kernel-libipsec plugin uses TUN devices and libipsec to provide IPsec
835 processing in userland on Linux, FreeBSD and Mac OS X.
837 - The eap-radius plugin can now serve as an XAuth backend called xauth-radius,
838 directly verifying XAuth credentials using RADIUS User-Name/User-Password
839 attributes. This is more efficient than the existing xauth-eap+eap-radius
840 combination, and allows RADIUS servers without EAP support to act as AAA
843 - The new osx-attr plugin installs configuration attributes (currently DNS
844 servers) via SystemConfiguration on Mac OS X. The keychain plugin provides
845 certificates from the OS X keychain service.
847 - The sshkey plugin parses SSH public keys, which, together with the --agent
848 option for charon-cmd, allows the use of ssh-agent for authentication.
849 To configure SSH keys in ipsec.conf the left|rightrsasigkey options are
850 replaced with left|rightsigkey, which now take public keys in one of three
851 formats: SSH (RFC 4253, ssh: prefix), DNSKEY (RFC 3110, dns: prefix), and
852 PKCS#1 (the default, no prefix).
854 - Extraction of certificates and private keys from PKCS#12 files is now provided
855 by the new pkcs12 plugin or the openssl plugin. charon-cmd (--p12) as well
856 as charon (via P12 token in ipsec.secrets) can make use of this.
858 - IKEv2 can now negotiate transport mode and IPComp in NAT situations.
860 - IKEv2 exchange initiators now properly close an established IKE or CHILD_SA
861 on error conditions using an additional exchange, keeping state in sync
864 - Using a SQL database interface a Trusted Network Connect (TNC) Policy Manager
865 can generate specific measurement workitems for an arbitrary number of
866 Integrity Measurement Verifiers (IMVs) based on the history of the VPN user
869 - Several core classes in libstrongswan are now tested with unit tests. These
870 can be enabled with --enable-unit-tests and run with 'make check'. Coverage
871 reports can be generated with --enable-coverage and 'make coverage' (this
872 disables any optimization, so it should not be enabled when building
873 production releases).
875 - The leak-detective developer tool has been greatly improved. It works much
876 faster/stabler with multiple threads, does not use deprecated malloc hooks
877 anymore and has been ported to OS X.
879 - chunk_hash() is now based on SipHash-2-4 with a random key. This provides
880 better distribution and prevents hash flooding attacks when used with
883 - All default plugins implement the get_features() method to define features
884 and their dependencies. The plugin loader has been improved, so that plugins
885 in a custom load statement can be ordered freely or to express preferences
886 without being affected by dependencies between plugin features.
888 - A centralized thread can take care for watching multiple file descriptors
889 concurrently. This removes the need for a dedicated listener threads in
890 various plugins. The number of "reserved" threads for such tasks has been
891 reduced to about five, depending on the plugin configuration.
893 - Plugins that can be controlled by a UNIX socket IPC mechanism gained network
894 transparency. Third party applications querying these plugins now can use
895 TCP connections from a different host.
897 - libipsec now supports AES-GCM.
903 - Fixed a security vulnerability in the openssl plugin which was reported by
904 Kevin Wojtysiak. The vulnerability has been registered as CVE-2013-2944.
905 Before the fix, if the openssl plugin's ECDSA signature verification was used,
906 due to a misinterpretation of the error code returned by the OpenSSL
907 ECDSA_verify() function, an empty or zeroed signature was accepted as a
910 - The handling of a couple of other non-security relevant openssl return codes
913 - The tnc_ifmap plugin now publishes virtual IPv4 and IPv6 addresses via its
914 TCG TNC IF-MAP 2.1 interface.
916 - The charon.initiator_only option causes charon to ignore IKE initiation
919 - The openssl plugin can now use the openssl-fips library.
925 - The new ipseckey plugin enables authentication based on trustworthy public
926 keys stored as IPSECKEY resource records in the DNS and protected by DNSSEC.
927 To do so it uses a DNSSEC enabled resolver, like the one provided by the new
928 unbound plugin, which is based on libldns and libunbound. Both plugins were
929 created by Reto Guadagnini.
931 - Implemented the TCG TNC IF-IMV 1.4 draft making access requestor identities
932 available to an IMV. The OS IMV stores the AR identity together with the
933 device ID in the attest database.
935 - The openssl plugin now uses the AES-NI accelerated version of AES-GCM
936 if the hardware supports it.
938 - The eap-radius plugin can now assign virtual IPs to IKE clients using the
939 Framed-IP-Address attribute by using the "%radius" named pool in the
940 rightsourceip ipsec.conf option. Cisco Banner attributes are forwarded to
941 Unity-capable IKEv1 clients during mode config. charon now sends Interim
942 Accounting updates if requested by the RADIUS server, reports
943 sent/received packets in Accounting messages, and adds a Terminate-Cause
946 - The recently introduced "ipsec listcounters" command can report connection
947 specific counters by passing a connection name, and global or connection
948 counters can be reset by the "ipsec resetcounters" command.
950 - The strongSwan libpttls library provides an experimental implementation of
951 PT-TLS (RFC 6876), a Posture Transport Protocol over TLS.
953 - The charon systime-fix plugin can disable certificate lifetime checks on
954 embedded systems if the system time is obviously out of sync after bootup.
955 Certificates lifetimes get checked once the system time gets sane, closing
956 or reauthenticating connections using expired certificates.
958 - The "ikedscp" ipsec.conf option can set DiffServ code points on outgoing
961 - The new xauth-noauth plugin allows to use basic RSA or PSK authentication with
962 clients that cannot be configured without XAuth authentication. The plugin
963 simply concludes the XAuth exchange successfully without actually performing
964 any authentication. Therefore, to use this backend it has to be selected
965 explicitly with rightauth2=xauth-noauth.
967 - The new charon-tkm IKEv2 daemon delegates security critical operations to a
968 separate process. This has the benefit that the network facing daemon has no
969 knowledge of keying material used to protect child SAs. Thus subverting
970 charon-tkm does not result in the compromise of cryptographic keys.
971 The extracted functionality has been implemented from scratch in a minimal TCB
972 (trusted computing base) in the Ada programming language. Further information
973 can be found at http://www.codelabs.ch/tkm/.
978 - Implemented all IETF Standard PA-TNC attributes and an OS IMC/IMV
979 pair using them to transfer operating system information.
981 - The new "ipsec listcounters" command prints a list of global counter values
982 about received and sent IKE messages and rekeyings.
984 - A new lookip plugin can perform fast lookup of tunnel information using a
985 clients virtual IP and can send notifications about established or deleted
986 tunnels. The "ipsec lookip" command can be used to query such information
987 or receive notifications.
989 - The new error-notify plugin catches some common error conditions and allows
990 an external application to receive notifications for them over a UNIX socket.
992 - IKE proposals can now use a PRF algorithm different to that defined for
993 integrity protection. If an algorithm with a "prf" prefix is defined
994 explicitly (such as prfsha1 or prfsha256), no implicit PRF algorithm based on
995 the integrity algorithm is added to the proposal.
997 - The pkcs11 plugin can now load leftcert certificates from a smartcard for a
998 specific ipsec.conf conn section and cacert CA certificates for a specific ca
1001 - The load-tester plugin gained additional options for certificate generation
1002 and can load keys and multiple CA certificates from external files. It can
1003 install a dedicated outer IP address for each tunnel and tunnel initiation
1004 batches can be triggered and monitored externally using the
1005 "ipsec load-tester" tool.
1007 - PKCS#7 container parsing has been modularized, and the openssl plugin
1008 gained an alternative implementation to decrypt and verify such files.
1009 In contrast to our own DER parser, OpenSSL can handle BER files, which is
1010 required for interoperability of our scepclient with EJBCA.
1012 - Support for the proprietary IKEv1 fragmentation extension has been added.
1013 Fragments are always handled on receipt but only sent if supported by the peer
1014 and if enabled with the new fragmentation ipsec.conf option.
1016 - IKEv1 in charon can now parse certificates received in PKCS#7 containers and
1017 supports NAT traversal as used by Windows clients. Patches courtesy of
1020 - The new rdrand plugin provides a high quality / high performance random
1021 source using the Intel rdrand instruction found on Ivy Bridge processors.
1023 - The integration test environment was updated and now uses KVM and reproducible
1024 guest images based on Debian.
1030 - Introduced the sending of the standard IETF Assessment Result
1031 PA-TNC attribute by all strongSwan Integrity Measurement Verifiers.
1033 - Extended PTS Attestation IMC/IMV pair to provide full evidence of
1034 the Linux IMA measurement process. All pertinent file information
1035 of a Linux OS can be collected and stored in an SQL database.
1037 - The PA-TNC and PB-TNC protocols can now process huge data payloads
1038 >64 kB by distributing PA-TNC attributes over multiple PA-TNC messages
1039 and these messages over several PB-TNC batches. As long as no
1040 consolidated recommandation from all IMVs can be obtained, the TNC
1041 server requests more client data by sending an empty SDATA batch.
1043 - The rightgroups2 ipsec.conf option can require group membership during
1044 a second authentication round, for example during XAuth authentication
1045 against a RADIUS server.
1047 - The xauth-pam backend can authenticate IKEv1 XAuth and Hybrid authenticated
1048 clients against any PAM service. The IKEv2 eap-gtc plugin does not use
1049 PAM directly anymore, but can use any XAuth backend to verify credentials,
1050 including xauth-pam.
1052 - The new unity plugin brings support for some parts of the IKEv1 Cisco Unity
1053 Extension. As client, charon narrows traffic selectors to the received
1054 Split-Include attributes and automatically installs IPsec bypass policies
1055 for received Local-LAN attributes. As server, charon sends Split-Include
1056 attributes for leftsubnet definitions containing multiple subnets to Unity-
1059 - An EAP-Nak payload is returned by clients if the gateway requests an EAP
1060 method that the client does not support. Clients can also request a specific
1061 EAP method by configuring that method with leftauth.
1063 - The eap-dynamic plugin handles EAP-Nak payloads returned by clients and uses
1064 these to select a different EAP method supported/requested by the client.
1065 The plugin initially requests the first registered method or the first method
1066 configured with charon.plugins.eap-dynamic.preferred.
1068 - The new left/rightdns options specify connection specific DNS servers to
1069 request/respond in IKEv2 configuration payloads or IKEv2 mode config. leftdns
1070 can be any (comma separated) combination of %config4 and %config6 to request
1071 multiple servers, both for IPv4 and IPv6. rightdns takes a list of DNS server
1072 IP addresses to return.
1074 - The left/rightsourceip options now accept multiple addresses or pools.
1075 leftsourceip can be any (comma separated) combination of %config4, %config6
1076 or fixed IP addresses to request. rightsourceip accepts multiple explicitly
1077 specified or referenced named pools.
1079 - Multiple connections can now share a single address pool when they use the
1080 same definition in one of the rightsourceip pools.
1082 - The options charon.interfaces_ignore and charon.interfaces_use allow one to
1083 configure the network interfaces used by the daemon.
1085 - The kernel-netlink plugin supports the charon.install_virtual_ip_on option,
1086 which specifies the interface on which virtual IP addresses will be installed.
1087 If it is not specified the current behavior of using the outbound interface
1090 - The kernel-netlink plugin tries to keep the current source address when
1091 looking for valid routes to reach other hosts.
1093 - The autotools build has been migrated to use a config.h header. strongSwan
1094 development headers will get installed during "make install" if
1095 --with-dev-headers has been passed to ./configure.
1097 - All crypto primitives gained return values for most operations, allowing
1098 crypto backends to fail, for example when using hardware accelerators.
1104 - The charon IKE daemon gained experimental support for the IKEv1 protocol.
1105 Pluto has been removed from the 5.x series, and unless strongSwan is
1106 configured with --disable-ikev1 or --disable-ikev2, charon handles both
1107 keying protocols. The feature-set of IKEv1 in charon is almost on par with
1108 pluto, but currently does not support AH or bundled AH+ESP SAs. Beside
1109 RSA/ECDSA, PSK and XAuth, charon also supports the Hybrid authentication
1110 mode. Information for interoperability and migration is available at
1111 http://wiki.strongswan.org/projects/strongswan/wiki/CharonPlutoIKEv1.
1113 - Charon's bus_t has been refactored so that loggers and other listeners are
1114 now handled separately. The single lock was previously cause for deadlocks
1115 if extensive listeners, such as the one provided by the updown plugin, wanted
1116 to acquire locks that were held by other threads which in turn tried to log
1117 messages, and thus were waiting to acquire the same lock currently held by
1118 the thread calling the listener.
1119 The implemented changes also allow the use of a read/write-lock for the
1120 loggers which increases performance if multiple loggers are registered.
1121 Besides several interface changes this last bit also changes the semantics
1122 for loggers as these may now be called by multiple threads at the same time.
1124 - Source routes are reinstalled if interfaces are reactivated or IP addresses
1127 - The thread pool (processor_t) now has more control over the lifecycle of
1128 a job (see job.h for details). In particular, it now controls the destruction
1129 of jobs after execution and the cancellation of jobs during shutdown. Due to
1130 these changes the requeueing feature, previously available to callback_job_t
1131 only, is now available to all jobs (in addition to a new rescheduling
1134 - In addition to trustchain key strength definitions for different public key
1135 systems, the rightauth option now takes a list of signature hash algorithms
1136 considered save for trustchain validation. For example, the setting
1137 rightauth=rsa-2048-ecdsa-256-sha256-sha384-sha512 requires a trustchain
1138 that uses at least RSA-2048 or ECDSA-256 keys and certificate signatures
1139 using SHA-256 or better.
1145 - Fixed a security vulnerability in the gmp plugin. If this plugin was used
1146 for RSA signature verification an empty or zeroed signature was handled as
1149 - Fixed several issues with reauthentication and address updates.
1155 - The tnc-pdp plugin implements a RADIUS server interface allowing
1156 a strongSwan TNC server to act as a Policy Decision Point.
1158 - The eap-radius authentication backend enforces Session-Timeout attributes
1159 using RFC4478 repeated authentication and acts upon RADIUS Dynamic
1160 Authorization extensions, RFC 5176. Currently supported are disconnect
1161 requests and CoA messages containing a Session-Timeout.
1163 - The eap-radius plugin can forward arbitrary RADIUS attributes from and to
1164 clients using custom IKEv2 notify payloads. The new radattr plugin reads
1165 attributes to include from files and prints received attributes to the
1168 - Added support for untruncated MD5 and SHA1 HMACs in ESP as used in
1171 - The cmac plugin implements the AES-CMAC-96 and AES-CMAC-PRF-128 algorithms
1172 as defined in RFC 4494 and RFC 4615, respectively.
1174 - The resolve plugin automatically installs nameservers via resolvconf(8),
1175 if it is installed, instead of modifying /etc/resolv.conf directly.
1177 - The IKEv2 charon daemon supports now raw RSA public keys in RFC 3110
1178 DNSKEY and PKCS#1 file format.
1184 - Upgraded the TCG IF-IMC and IF-IMV C API to the upcoming version 1.3
1185 which supports IF-TNCCS 2.0 long message types, the exclusive flags
1186 and multiple IMC/IMV IDs. Both the TNC Client and Server as well as
1187 the "Test", "Scanner", and "Attestation" IMC/IMV pairs were updated.
1189 - Fully implemented the "TCG Attestation PTS Protocol: Binding to IF-M"
1190 standard (TLV-based messages only). TPM-based remote attestation of
1191 Linux IMA (Integrity Measurement Architecture) possible. Measurement
1192 reference values are automatically stored in an SQLite database.
1194 - The EAP-RADIUS authentication backend supports RADIUS accounting. It sends
1195 start/stop messages containing Username, Framed-IP and Input/Output-Octets
1196 attributes and has been tested against FreeRADIUS and Microsoft NPS.
1198 - Added support for PKCS#8 encoded private keys via the libstrongswan
1199 pkcs8 plugin. This is the default format used by some OpenSSL tools since
1200 version 1.0.0 (e.g. openssl req with -keyout).
1202 - Added session resumption support to the strongSwan TLS stack.
1208 - Because of changing checksums before and after installation which caused
1209 the integrity tests to fail we avoided directly linking libsimaka, libtls and
1210 libtnccs to those libcharon plugins which make use of these dynamic libraries.
1211 Instead we linked the libraries to the charon daemon. Unfortunately Ubuntu
1212 11.10 activated the --as-needed ld option which discards explicit links
1213 to dynamic libraries that are not actually used by the charon daemon itself,
1214 thus causing failures during the loading of the plugins which depend on these
1215 libraries for resolving external symbols.
1217 - Therefore our approach of computing integrity checksums for plugins had to be
1218 changed radically by moving the hash generation from the compilation to the
1219 post-installation phase.
1225 - The new libstrongswan certexpire plugin collects expiration information of
1226 all used certificates and exports them to CSV files. It either directly
1227 exports them or uses cron style scheduling for batch exports.
1229 - starter passes unresolved hostnames to charon, allowing it to do name
1230 resolution not before the connection attempt. This is especially useful with
1231 connections between hosts using dynamic IP addresses. Thanks to Mirko Parthey
1232 for the initial patch.
1234 - The android plugin can now be used without the Android frontend patch and
1235 provides DNS server registration and logging to logcat.
1237 - Pluto and starter (plus stroke and whack) have been ported to Android.
1239 - Support for ECDSA private and public key operations has been added to the
1240 pkcs11 plugin. The plugin now also provides DH and ECDH via PKCS#11 and can
1241 use tokens as random number generators (RNG). By default only private key
1242 operations are enabled, more advanced features have to be enabled by their
1243 option in strongswan.conf. This also applies to public key operations (even
1244 for keys not stored on the token) which were enabled by default before.
1246 - The libstrongswan plugin system now supports detailed plugin dependencies.
1247 Many plugins have been extended to export its capabilities and requirements.
1248 This allows the plugin loader to resolve plugin loading order automatically,
1249 and in future releases, to dynamically load the required features on demand.
1250 Existing third party plugins are source (but not binary) compatible if they
1251 properly initialize the new get_features() plugin function to NULL.
1253 - The tnc-ifmap plugin implements a TNC IF-MAP 2.0 client which can deliver
1254 metadata about IKE_SAs via a SOAP interface to a MAP server. The tnc-ifmap
1255 plugin requires the Apache Axis2/C library.
1261 - Our private libraries (e.g. libstrongswan) are not installed directly in
1262 prefix/lib anymore. Instead a subdirectory is used (prefix/lib/ipsec/ by
1263 default). The plugins directory is also moved from libexec/ipsec/ to that
1266 - The dynamic IMC/IMV libraries were moved from the plugins directory to
1267 a new imcvs directory in the prefix/lib/ipsec/ subdirectory.
1269 - Job priorities were introduced to prevent thread starvation caused by too
1270 many threads handling blocking operations (such as CRL fetching). Refer to
1271 strongswan.conf(5) for details.
1273 - Two new strongswan.conf options allow to fine-tune performance on IKEv2
1274 gateways by dropping IKE_SA_INIT requests on high load.
1276 - IKEv2 charon daemon supports start PASS and DROP shunt policies
1277 preventing traffic to go through IPsec connections. Installation of the
1278 shunt policies either via the XFRM netfilter or PFKEYv2 IPsec kernel
1281 - The history of policies installed in the kernel is now tracked so that e.g.
1282 trap policies are correctly updated when reauthenticated SAs are terminated.
1284 - IMC/IMV Scanner pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1285 Using "netstat -l" the IMC scans open listening ports on the TNC client
1286 and sends a port list to the IMV which based on a port policy decides if
1287 the client is admitted to the network.
1288 (--enable-imc-scanner/--enable-imv-scanner).
1290 - IMC/IMV Test pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1291 (--enable-imc-test/--enable-imv-test).
1293 - The IKEv2 close action does not use the same value as the ipsec.conf dpdaction
1294 setting, but the value defined by its own closeaction keyword. The action
1295 is triggered if the remote peer closes a CHILD_SA unexpectedly.
1301 - The whitelist plugin for the IKEv2 daemon maintains an in-memory identity
1302 whitelist. Any connection attempt of peers not whitelisted will get rejected.
1303 The 'ipsec whitelist' utility provides a simple command line frontend for
1304 whitelist administration.
1306 - The duplicheck plugin provides a specialized form of duplicate checking,
1307 doing a liveness check on the old SA and optionally notify a third party
1308 application about detected duplicates.
1310 - The coupling plugin permanently couples two or more devices by limiting
1311 authentication to previously used certificates.
1313 - In the case that the peer config and child config don't have the same name
1314 (usually in SQL database defined connections), ipsec up|route <peer config>
1315 starts|routes all associated child configs and ipsec up|route <child config>
1316 only starts|routes the specific child config.
1318 - fixed the encoding and parsing of X.509 certificate policy statements (CPS).
1320 - Duncan Salerno contributed the eap-sim-pcsc plugin implementing a
1321 pcsc-lite based SIM card backend.
1323 - The eap-peap plugin implements the EAP PEAP protocol. Interoperates
1324 successfully with a FreeRADIUS server and Windows 7 Agile VPN clients.
1326 - The IKEv2 daemon charon rereads strongswan.conf on SIGHUP and instructs
1327 all plugins to reload. Currently only the eap-radius and the attr plugins
1328 support configuration reloading.
1330 - Added userland support to the IKEv2 daemon for Extended Sequence Numbers
1331 support coming with Linux 2.6.39. To enable ESN on a connection, add
1332 the 'esn' keyword to the proposal. The default proposal uses 32-bit sequence
1333 numbers only ('noesn'), and the same value is used if no ESN mode is
1334 specified. To negotiate ESN support with the peer, include both, e.g.
1335 esp=aes128-sha1-esn-noesn.
1337 - In addition to ESN, Linux 2.6.39 gained support for replay windows larger
1338 than 32 packets. The new global strongswan.conf option 'charon.replay_window'
1339 configures the size of the replay window, in packets.
1345 - Sansar Choinyambuu implemented the RFC 5793 Posture Broker Protocol (BP)
1346 compatible with Trusted Network Connect (TNC). The TNCCS 2.0 protocol
1347 requires the tnccs_20, tnc_imc and tnc_imv plugins but does not depend
1348 on the libtnc library. Any available IMV/IMC pairs conforming to the
1349 Trusted Computing Group's TNC-IF-IMV/IMC 1.2 interface specification
1350 can be loaded via /etc/tnc_config.
1352 - Re-implemented the TNCCS 1.1 protocol by using the tnc_imc and tnc_imv
1353 in place of the external libtnc library.
1355 - The tnccs_dynamic plugin loaded on a TNC server in addition to the
1356 tnccs_11 and tnccs_20 plugins, dynamically detects the IF-TNCCS
1357 protocol version used by a TNC client and invokes an instance of
1358 the corresponding protocol stack.
1360 - IKE and ESP proposals can now be stored in an SQL database using a
1361 new proposals table. The start_action field in the child_configs
1362 tables allows the automatic starting or routing of connections stored
1365 - The new certificate_authorities and certificate_distribution_points
1366 tables make it possible to store CRL and OCSP Certificate Distribution
1367 points in an SQL database.
1369 - The new 'include' statement allows to recursively include other files in
1370 strongswan.conf. Existing sections and values are thereby extended and
1371 replaced, respectively.
1373 - Due to the changes in the parser for strongswan.conf, the configuration
1374 syntax for the attr plugin has changed. Previously, it was possible to
1375 specify multiple values of a specific attribute type by adding multiple
1376 key/value pairs with the same key (e.g. dns) to the plugins.attr section.
1377 Because values with the same key now replace previously defined values
1378 this is not possible anymore. As an alternative, multiple values can be
1379 specified by separating them with a comma (e.g. dns = 1.2.3.4, 2.3.4.5).
1381 - ipsec listalgs now appends (set in square brackets) to each crypto
1382 algorithm listed the plugin that registered the function.
1384 - Traffic Flow Confidentiality padding supported with Linux 2.6.38 can be used
1385 by the IKEv2 daemon. The ipsec.conf 'tfc' keyword pads all packets to a given
1386 boundary, the special value '%mtu' pads all packets to the path MTU.
1388 - The new af-alg plugin can use various crypto primitives of the Linux Crypto
1389 API using the AF_ALG interface introduced with 2.6.38. This removes the need
1390 for additional userland implementations of symmetric cipher, hash, hmac and
1393 - The IKEv2 daemon supports the INITIAL_CONTACT notify as initiator and
1394 responder. The notify is sent when initiating configurations with a unique
1395 policy, set in ipsec.conf via the global 'uniqueids' option.
1397 - The conftest conformance testing framework enables the IKEv2 stack to perform
1398 many tests using a distinct tool and configuration frontend. Various hooks
1399 can alter reserved bits, flags, add custom notifies and proposals, reorder
1400 or drop messages and much more. It is enabled using the --enable-conftest
1403 - The new libstrongswan constraints plugin provides advanced X.509 constraint
1404 checking. In addition to X.509 pathLen constraints, the plugin checks for
1405 nameConstraints and certificatePolicies, including policyMappings and
1406 policyConstraints. The x509 certificate plugin and the pki tool have been
1407 enhanced to support these extensions. The new left/rightcertpolicy ipsec.conf
1408 connection keywords take OIDs a peer certificate must have.
1410 - The left/rightauth ipsec.conf keywords accept values with a minimum strength
1411 for trustchain public keys in bits, such as rsa-2048 or ecdsa-256.
1413 - The revocation and x509 libstrongswan plugins and the pki tool gained basic
1414 support for delta CRLs.
1420 - IMPORTANT: the default keyexchange mode 'ike' is changing with release 4.5
1421 from 'ikev1' to 'ikev2', thus commemorating the five year anniversary of the
1422 IKEv2 RFC 4306 and its mature successor RFC 5996. The time has definitively
1423 come for IKEv1 to go into retirement and to cede its place to the much more
1424 robust, powerful and versatile IKEv2 protocol!
1426 - Added new ctr, ccm and gcm plugins providing Counter, Counter with CBC-MAC
1427 and Galois/Counter Modes based on existing CBC implementations. These
1428 new plugins bring support for AES and Camellia Counter and CCM algorithms
1429 and the AES GCM algorithms for use in IKEv2.
1431 - The new pkcs11 plugin brings full Smartcard support to the IKEv2 daemon and
1432 the pki utility using one or more PKCS#11 libraries. It currently supports
1433 RSA private and public key operations and loads X.509 certificates from
1436 - Implemented a general purpose TLS stack based on crypto and credential
1437 primitives of libstrongswan. libtls supports TLS versions 1.0, 1.1 and 1.2,
1438 ECDHE-ECDSA/RSA, DHE-RSA and RSA key exchange algorithms and RSA/ECDSA based
1439 client authentication.
1441 - Based on libtls, the eap-tls plugin brings certificate based EAP
1442 authentication for client and server. It is compatible to Windows 7 IKEv2
1443 Smartcard authentication and the OpenSSL based FreeRADIUS EAP-TLS backend.
1445 - Implemented the TNCCS 1.1 Trusted Network Connect protocol using the
1446 libtnc library on the strongSwan client and server side via the tnccs_11
1447 plugin and optionally connecting to a TNC@FHH-enhanced FreeRADIUS AAA server.
1448 Depending on the resulting TNC Recommendation, strongSwan clients are granted
1449 access to a network behind a strongSwan gateway (allow), are put into a
1450 remediation zone (isolate) or are blocked (none), respectively. Any number
1451 of Integrity Measurement Collector/Verifier pairs can be attached
1452 via the tnc-imc and tnc-imv charon plugins.
1454 - The IKEv1 daemon pluto now uses the same kernel interfaces as the IKEv2
1455 daemon charon. As a result of this, pluto now supports xfrm marks which
1456 were introduced in charon with 4.4.1.
1458 - Applets for Maemo 5 (Nokia) allow to easily configure and control IKEv2
1459 based VPN connections with EAP authentication on supported devices.
1461 - The RADIUS plugin eap-radius now supports multiple RADIUS servers for
1462 redundant setups. Servers are selected by a defined priority, server load and
1465 - The simple led plugin controls hardware LEDs through the Linux LED subsystem.
1466 It currently shows activity of the IKE daemon and is a good example how to
1467 implement a simple event listener.
1469 - Improved MOBIKE behavior in several corner cases, for instance, if the
1470 initial responder moves to a different address.
1472 - Fixed left-/rightnexthop option, which was broken since 4.4.0.
1474 - Fixed a bug not releasing a virtual IP address to a pool if the XAUTH
1475 identity was different from the IKE identity.
1477 - Fixed the alignment of ModeConfig messages on 4-byte boundaries in the
1478 case where the attributes are not a multiple of 4 bytes (e.g. Cisco's
1481 - Fixed the interoperability of the socket_raw and socket_default
1484 - Added man page for strongswan.conf
1490 - Support of xfrm marks in IPsec SAs and IPsec policies introduced
1491 with the Linux 2.6.34 kernel. For details see the example scenarios
1492 ikev2/nat-two-rw-mark, ikev2/rw-nat-mark-in-out and ikev2/net2net-psk-dscp.
1494 - The PLUTO_MARK_IN and PLUTO_ESP_ENC environment variables can be used
1495 in a user-specific updown script to set marks on inbound ESP or
1498 - The openssl plugin now supports X.509 certificate and CRL functions.
1500 - OCSP/CRL checking in IKEv2 has been moved to the revocation plugin, enabled
1501 by default. Please update manual load directives in strongswan.conf.
1503 - RFC3779 ipAddrBlock constraint checking has been moved to the addrblock
1504 plugin, disabled by default. Enable it and update manual load directives
1505 in strongswan.conf, if required.
1507 - The pki utility supports CRL generation using the --signcrl command.
1509 - The ipsec pki --self, --issue and --req commands now support output in
1510 PEM format using the --outform pem option.
1512 - The major refactoring of the IKEv1 Mode Config functionality now allows
1513 the transport and handling of any Mode Config attribute.
1515 - The RADIUS proxy plugin eap-radius now supports multiple servers. Configured
1516 servers are chosen randomly, with the option to prefer a specific server.
1517 Non-responding servers are degraded by the selection process.
1519 - The ipsec pool tool manages arbitrary configuration attributes stored
1520 in an SQL database. ipsec pool --help gives the details.
1522 - The new eap-simaka-sql plugin acts as a backend for EAP-SIM and EAP-AKA,
1523 reading triplets/quintuplets from an SQL database.
1525 - The High Availability plugin now supports a HA enabled in-memory address
1526 pool and Node reintegration without IKE_SA rekeying. The latter allows
1527 clients without IKE_SA rekeying support to keep connected during
1528 reintegration. Additionally, many other issues have been fixed in the ha
1531 - Fixed a potential remote code execution vulnerability resulting from
1532 the misuse of snprintf(). The vulnerability is exploitable by
1533 unauthenticated users.
1539 - The IKEv2 High Availability plugin has been integrated. It provides
1540 load sharing and failover capabilities in a cluster of currently two nodes,
1541 based on an extend ClusterIP kernel module. More information is available at
1542 http://wiki.strongswan.org/projects/strongswan/wiki/HighAvailability.
1543 The development of the High Availability functionality was sponsored by
1544 secunet Security Networks AG.
1546 - Added IKEv1 and IKEv2 configuration support for the AES-GMAC
1547 authentication-only ESP cipher. Our aes_gmac kernel patch or a Linux
1548 2.6.34 kernel is required to make AES-GMAC available via the XFRM
1551 - Added support for Diffie-Hellman groups 22, 23 and 24 to the gmp, gcrypt
1552 and openssl plugins, usable by both pluto and charon. The new proposal
1553 keywords are modp1024s160, modp2048s224 and modp2048s256. Thanks to Joy Latten
1554 from IBM for his contribution.
1556 - The IKEv1 pluto daemon supports RAM-based virtual IP pools using
1557 the rightsourceip directive with a subnet from which addresses
1560 - The ipsec pki --gen and --pub commands now allow the output of
1561 private and public keys in PEM format using the --outform pem
1562 command line option.
1564 - The new DHCP plugin queries virtual IP addresses for clients from a DHCP
1565 server using broadcasts, or a defined server using the
1566 charon.plugins.dhcp.server strongswan.conf option. DNS/WINS server information
1567 is additionally served to clients if the DHCP server provides such
1568 information. The plugin is used in ipsec.conf configurations having
1569 rightsourceip set to %dhcp.
1571 - A new plugin called farp fakes ARP responses for virtual IP addresses
1572 handed out to clients from the IKEv2 daemon charon. The plugin lets a
1573 road-warrior act as a client on the local LAN if it uses a virtual IP
1574 from the responders subnet, e.g. acquired using the DHCP plugin.
1576 - The existing IKEv2 socket implementations have been migrated to the
1577 socket-default and the socket-raw plugins. The new socket-dynamic plugin
1578 binds sockets dynamically to ports configured via the left-/rightikeport
1579 ipsec.conf connection parameters.
1581 - The android charon plugin stores received DNS server information as "net.dns"
1582 system properties, as used by the Android platform.
1588 - The IKEv2 daemon supports RFC 3779 IP address block constraints
1589 carried as a critical X.509v3 extension in the peer certificate.
1591 - The ipsec pool --add|del dns|nbns command manages DNS and NBNS name
1592 server entries that are sent via the IKEv1 Mode Config or IKEv2
1593 Configuration Payload to remote clients.
1595 - The Camellia cipher can be used as an IKEv1 encryption algorithm.
1597 - The IKEv1 and IKEV2 daemons now check certificate path length constraints.
1599 - The new ipsec.conf conn option "inactivity" closes a CHILD_SA if no traffic
1600 was sent or received within the given interval. To close the complete IKE_SA
1601 if its only CHILD_SA was inactive, set the global strongswan.conf option
1602 "charon.inactivity_close_ike" to yes.
1604 - More detailed IKEv2 EAP payload information in debug output
1606 - IKEv2 EAP-SIM and EAP-AKA share joint libsimaka library
1608 - Added required userland changes for proper SHA256 and SHA384/512 in ESP that
1609 will be introduced with Linux 2.6.33. The "sha256"/"sha2_256" keyword now
1610 configures the kernel with 128 bit truncation, not the non-standard 96
1611 bit truncation used by previous releases. To use the old 96 bit truncation
1612 scheme, the new "sha256_96" proposal keyword has been introduced.
1614 - Fixed IPComp in tunnel mode, stripping out the duplicated outer header. This
1615 change makes IPcomp tunnel mode connections incompatible with previous
1616 releases; disable compression on such tunnels.
1618 - Fixed BEET mode connections on recent kernels by installing SAs with
1619 appropriate traffic selectors, based on a patch by Michael Rossberg.
1621 - Using extensions (such as BEET mode) and crypto algorithms (such as twofish,
1622 serpent, sha256_96) allocated in the private use space now require that we
1623 know its meaning, i.e. we are talking to strongSwan. Use the new
1624 "charon.send_vendor_id" option in strongswan.conf to let the remote peer know
1627 - Experimental support for draft-eronen-ipsec-ikev2-eap-auth, where the
1628 responder omits public key authentication in favor of a mutual authentication
1629 method. To enable EAP-only authentication, set rightauth=eap on the responder
1630 to rely only on the MSK constructed AUTH payload. This not-yet standardized
1631 extension requires the strongSwan vendor ID introduced above.
1633 - The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus
1634 allowing interoperability.
1640 - The IKEv1 pluto daemon can now use SQL-based address pools to deal out
1641 virtual IP addresses as a Mode Config server. The pool capability has been
1642 migrated from charon's sql plugin to a new attr-sql plugin which is loaded
1643 by libstrongswan and which can be used by both daemons either with a SQLite
1644 or MySQL database and the corresponding plugin.
1646 - Plugin names have been streamlined: EAP plugins now have a dash after eap
1647 (e.g. eap-sim), as it is used with the --enable-eap-sim ./configure option.
1648 Plugin configuration sections in strongswan.conf now use the same name as the
1649 plugin itself (i.e. with a dash). Make sure to update "load" directives and
1650 the affected plugin sections in existing strongswan.conf files.
1652 - The private/public key parsing and encoding has been split up into
1653 separate pkcs1, pgp, pem and dnskey plugins. The public key implementation
1654 plugins gmp, gcrypt and openssl can all make use of them.
1656 - The EAP-AKA plugin can use different backends for USIM/quintuplet
1657 calculations, very similar to the EAP-SIM plugin. The existing 3GPP2 software
1658 implementation has been migrated to a separate plugin.
1660 - The IKEv2 daemon charon gained basic PGP support. It can use locally installed
1661 peer certificates and can issue signatures based on RSA private keys.
1663 - The new 'ipsec pki' tool provides a set of commands to maintain a public
1664 key infrastructure. It currently supports operations to create RSA and ECDSA
1665 private/public keys, calculate fingerprints and issue or verify certificates.
1667 - Charon uses a monotonic time source for statistics and job queueing, behaving
1668 correctly if the system time changes (e.g. when using NTP).
1670 - In addition to time based rekeying, charon supports IPsec SA lifetimes based
1671 on processed volume or number of packets. They new ipsec.conf parameters
1672 'lifetime' (an alias to 'keylife'), 'lifebytes' and 'lifepackets' handle
1673 SA timeouts, while the parameters 'margintime' (an alias to rekeymargin),
1674 'marginbytes' and 'marginpackets' trigger the rekeying before a SA expires.
1675 The existing parameter 'rekeyfuzz' affects all margins.
1677 - If no CA/Gateway certificate is specified in the NetworkManager plugin,
1678 charon uses a set of trusted root certificates preinstalled by distributions.
1679 The directory containing CA certificates can be specified using the
1680 --with-nm-ca-dir=path configure option.
1682 - Fixed the encoding of the Email relative distinguished name in left|rightid
1685 - Fixed the broken parsing of PKCS#7 wrapped certificates by the pluto daemon.
1687 - Fixed smartcard-based authentication in the pluto daemon which was broken by
1688 the ECDSA support introduced with the 4.3.2 release.
1690 - A patch contributed by Heiko Hund fixes mixed IPv6 in IPv4 and vice versa
1691 tunnels established with the IKEv1 pluto daemon.
1693 - The pluto daemon now uses the libstrongswan x509 plugin for certificates and
1694 CRls and the struct id type was replaced by identification_t used by charon
1695 and the libstrongswan library.
1701 - IKEv2 charon daemon ported to FreeBSD and Mac OS X. Installation details can
1702 be found on wiki.strongswan.org.
1704 - ipsec statusall shows the number of bytes transmitted and received over
1705 ESP connections configured by the IKEv2 charon daemon.
1707 - The IKEv2 charon daemon supports include files in ipsec.secrets.
1713 - The configuration option --enable-integrity-test plus the strongswan.conf
1714 option libstrongswan.integrity_test = yes activate integrity tests
1715 of the IKE daemons charon and pluto, libstrongswan and all loaded
1716 plugins. Thus dynamic library misconfigurations and non-malicious file
1717 manipulations can be reliably detected.
1719 - The new default setting libstrongswan.ecp_x_coordinate_only=yes allows
1720 IKEv1 interoperability with MS Windows using the ECP DH groups 19 and 20.
1722 - The IKEv1 pluto daemon now supports the AES-CCM and AES-GCM ESP
1723 authenticated encryption algorithms.
1725 - The IKEv1 pluto daemon now supports V4 OpenPGP keys.
1727 - The RDN parser vulnerability discovered by Orange Labs research team
1728 was not completely fixed in version 4.3.2. Some more modifications
1729 had to be applied to the asn1_length() function to make it robust.
1735 - The new gcrypt plugin provides symmetric cipher, hasher, RNG, Diffie-Hellman
1736 and RSA crypto primitives using the LGPL licensed GNU gcrypt library.
1738 - libstrongswan features an integrated crypto selftest framework for registered
1739 algorithms. The test-vector plugin provides a first set of test vectors and
1740 allows pluto and charon to rely on tested crypto algorithms.
1742 - pluto can now use all libstrongswan plugins with the exception of x509 and xcbc.
1743 Thanks to the openssl plugin, the ECP Diffie-Hellman groups 19, 20, 21, 25, and
1744 26 as well as ECDSA-256, ECDSA-384, and ECDSA-521 authentication can be used
1747 - Applying their fuzzing tool, the Orange Labs vulnerability research team found
1748 another two DoS vulnerabilities, one in the rather old ASN.1 parser of Relative
1749 Distinguished Names (RDNs) and a second one in the conversion of ASN.1 UTCTIME
1750 and GENERALIZEDTIME strings to a time_t value.
1756 - The nm plugin now passes DNS/NBNS server information to NetworkManager,
1757 allowing a gateway administrator to set DNS/NBNS configuration on clients
1760 - The nm plugin also accepts CA certificates for gateway authentication. If
1761 a CA certificate is configured, strongSwan uses the entered gateway address
1762 as its idenitity, requiring the gateways certificate to contain the same as
1763 subjectAltName. This allows a gateway administrator to deploy the same
1764 certificates to Windows 7 and NetworkManager clients.
1766 - The command ipsec purgeike deletes IKEv2 SAs that don't have a CHILD SA.
1767 The command ipsec down <conn>{n} deletes CHILD SA instance n of connection
1768 <conn> whereas ipsec down <conn>{*} deletes all CHILD SA instances.
1769 The command ipsec down <conn>[n] deletes IKE SA instance n of connection
1770 <conn> plus dependent CHILD SAs whereas ipsec down <conn>[*] deletes all
1771 IKE SA instances of connection <conn>.
1773 - Fixed a regression introduced in 4.3.0 where EAP authentication calculated
1774 the AUTH payload incorrectly. Further, the EAP-MSCHAPv2 MSK key derivation
1775 has been updated to be compatible with the Windows 7 Release Candidate.
1777 - Refactored installation of triggering policies. Routed policies are handled
1778 outside of IKE_SAs to keep them installed in any case. A tunnel gets
1779 established only once, even if initiation is delayed due network outages.
1781 - Improved the handling of multiple acquire signals triggered by the kernel.
1783 - Fixed two DoS vulnerabilities in the charon daemon that were discovered by
1784 fuzzing techniques: 1) Sending a malformed IKE_SA_INIT request leaved an
1785 incomplete state which caused a null pointer dereference if a subsequent
1786 CREATE_CHILD_SA request was sent. 2) Sending an IKE_AUTH request with either
1787 a missing TSi or TSr payload caused a null pointer derefence because the
1788 checks for TSi and TSr were interchanged. The IKEv2 fuzzer used was
1789 developed by the Orange Labs vulnerability research team. The tool was
1790 initially written by Gabriel Campana and is now maintained by Laurent Butti.
1792 - Added support for AES counter mode in ESP in IKEv2 using the proposal
1793 keywords aes128ctr, aes192ctr and aes256ctr.
1795 - Further progress in refactoring pluto: Use of the curl and ldap plugins
1796 for fetching crls and OCSP. Use of the random plugin to get keying material
1797 from /dev/random or /dev/urandom. Use of the openssl plugin as an alternative
1798 to the aes, des, sha1, sha2, and md5 plugins. The blowfish, twofish, and
1799 serpent encryption plugins are now optional and are not enabled by default.
1805 - Support for the IKEv2 Multiple Authentication Exchanges extension (RFC4739).
1806 Initiators and responders can use several authentication rounds (e.g. RSA
1807 followed by EAP) to authenticate. The new ipsec.conf leftauth/rightauth and
1808 leftauth2/rightauth2 parameters define own authentication rounds or setup
1809 constraints for the remote peer. See the ipsec.conf man page for more detials.
1811 - If glibc printf hooks (register_printf_function) are not available,
1812 strongSwan can use the vstr string library to run on non-glibc systems.
1814 - The IKEv2 charon daemon can now configure the ESP CAMELLIA-CBC cipher
1815 (esp=camellia128|192|256).
1817 - Refactored the pluto and scepclient code to use basic functions (memory
1818 allocation, leak detective, chunk handling, printf_hooks, strongswan.conf
1819 attributes, ASN.1 parser, etc.) from the libstrongswan library.
1821 - Up to two DNS and WINS servers to be sent via IKEv1 ModeConfig can be
1822 configured in the pluto section of strongswan.conf.
1828 - The new server-side EAP RADIUS plugin (--enable-eap-radius)
1829 relays EAP messages to and from a RADIUS server. Successfully
1830 tested with with a freeradius server using EAP-MD5 and EAP-SIM.
1832 - A vulnerability in the Dead Peer Detection (RFC 3706) code was found by
1833 Gerd v. Egidy <gerd.von.egidy@intra2net.com> of Intra2net AG affecting
1834 all Openswan and strongSwan releases. A malicious (or expired ISAKMP)
1835 R_U_THERE or R_U_THERE_ACK Dead Peer Detection packet can cause the
1836 pluto IKE daemon to crash and restart. No authentication or encryption
1837 is required to trigger this bug. One spoofed UDP packet can cause the
1838 pluto IKE daemon to restart and be unresponsive for a few seconds while
1839 restarting. This DPD null state vulnerability has been officially
1840 registered as CVE-2009-0790 and is fixed by this release.
1842 - ASN.1 to time_t conversion caused a time wrap-around for
1843 dates after Jan 18 03:14:07 UTC 2038 on 32-bit platforms.
1844 As a workaround such dates are set to the maximum representable
1845 time, i.e. Jan 19 03:14:07 UTC 2038.
1847 - Distinguished Names containing wildcards (*) are not sent in the
1848 IDr payload anymore.
1854 - Fixed a use-after-free bug in the DPD timeout section of the
1855 IKEv1 pluto daemon which sporadically caused a segfault.
1857 - Fixed a crash in the IKEv2 charon daemon occurring with
1858 mixed RAM-based and SQL-based virtual IP address pools.
1860 - Fixed ASN.1 parsing of algorithmIdentifier objects where the
1861 parameters field is optional.
1863 - Ported nm plugin to NetworkManager 7.1.
1869 - Support of the EAP-MSCHAPv2 protocol enabled by the option
1870 --enable-eap-mschapv2. Requires the MD4 hash algorithm enabled
1871 either by --enable-md4 or --enable-openssl.
1873 - Assignment of up to two DNS and up to two WINS servers to peers via
1874 the IKEv2 Configuration Payload (CP). The IPv4 or IPv6 nameserver
1875 addresses are defined in strongswan.conf.
1877 - The strongSwan applet for the Gnome NetworkManager is now built and
1878 distributed as a separate tarball under the name NetworkManager-strongswan.
1884 - Fixed ESP NULL encryption broken by the refactoring of keymat.c.
1885 Also introduced proper initialization and disposal of keying material.
1887 - Fixed the missing listing of connection definitions in ipsec statusall
1888 broken by an unfortunate local variable overload.
1894 - Several performance improvements to handle thousands of tunnels with almost
1895 linear upscaling. All relevant data structures have been replaced by faster
1896 counterparts with better lookup times.
1898 - Better parallelization to run charon on multiple cores. Due to improved
1899 resource locking and other optimizations the daemon can take full
1900 advantage of 16 or even more cores.
1902 - The load-tester plugin can use a NULL Diffie-Hellman group and simulate
1903 unique identities and certificates by signing peer certificates using a CA
1906 - The redesigned stroke in-memory IP pool handles leases. The "ipsec leases"
1907 command queries assigned leases.
1909 - Added support for smartcards in charon by using the ENGINE API provided by
1910 OpenSSL, based on patches by Michael Roßberg.
1912 - The Padlock plugin supports the hardware RNG found on VIA CPUs to provide a
1913 reliable source of randomness.
1918 - Flexible configuration of logging subsystem allowing to log to multiple
1919 syslog facilities or to files using fine-grained log levels for each target.
1921 - Load testing plugin to do stress testing of the IKEv2 daemon against self
1922 or another host. Found and fixed issues during tests in the multi-threaded
1923 use of the OpenSSL plugin.
1925 - Added profiling code to synchronization primitives to find bottlenecks if
1926 running on multiple cores. Found and fixed an issue where parts of the
1927 Diffie-Hellman calculation acquired an exclusive lock. This greatly improves
1928 parallelization to multiple cores.
1930 - updown script invocation has been separated into a plugin of its own to
1931 further slim down the daemon core.
1933 - Separated IKE_SA/CHILD_SA key derivation process into a closed system,
1934 allowing future implementations to use a secured environment in e.g. kernel
1937 - The kernel interface of charon has been modularized. XFRM NETLINK (default)
1938 and PFKEY (--enable-kernel-pfkey) interface plugins for the native IPsec
1939 stack of the Linux 2.6 kernel as well as a PFKEY interface for the KLIPS
1940 IPsec stack (--enable-kernel-klips) are provided.
1942 - Basic Mobile IPv6 support has been introduced, securing Binding Update
1943 messages as well as tunneled traffic between Mobile Node and Home Agent.
1944 The installpolicy=no option allows peaceful cooperation with a dominant
1945 mip6d daemon and the new type=transport_proxy implements the special MIPv6
1946 IPsec transport proxy mode where the IKEv2 daemon uses the Care-of-Address
1947 but the IPsec SA is set up for the Home Address.
1949 - Implemented migration of Mobile IPv6 connections using the KMADDRESS
1950 field contained in XFRM_MSG_MIGRATE messages sent by the mip6d daemon
1951 via the Linux 2.6.28 (or appropriately patched) kernel.
1957 - IKEv2 charon daemon supports authentication based on raw public keys
1958 stored in the SQL database backend. The ipsec listpubkeys command
1959 lists the available raw public keys via the stroke interface.
1961 - Several MOBIKE improvements: Detect changes in NAT mappings in DPD exchanges,
1962 handle events if kernel detects NAT mapping changes in UDP-encapsulated
1963 ESP packets (requires kernel patch), reuse old addresses in MOBIKE updates as
1964 long as possible and other fixes.
1966 - Fixed a bug in addr_in_subnet() which caused insertion of wrong source
1967 routes for destination subnets having netwmasks not being a multiple of 8 bits.
1968 Thanks go to Wolfgang Steudel, TU Ilmenau for reporting this bug.
1974 - Fixed a Denial-of-Service vulnerability where an IKE_SA_INIT message with
1975 a KE payload containing zeroes only can cause a crash of the IKEv2 charon
1976 daemon due to a NULL pointer returned by the mpz_export() function of the
1977 GNU Multiprecision Library (GMP). Thanks go to Mu Dynamics Research Labs
1978 for making us aware of this problem.
1980 - The new agent plugin provides a private key implementation on top of an
1983 - The NetworkManager plugin has been extended to support certificate client
1984 authentication using RSA keys loaded from a file or using ssh-agent.
1986 - Daemon capability dropping has been ported to libcap and must be enabled
1987 explicitly --with-capabilities=libcap. Future version will support the
1988 newer libcap2 library.
1990 - ipsec listalgs lists the IKEv2 cryptografic algorithms registered with the
1991 charon keying daemon.
1997 - A NetworkManager plugin allows GUI-based configuration of road-warrior
1998 clients in a simple way. It features X509 based gateway authentication
1999 and EAP client authentication, tunnel setup/teardown and storing passwords
2000 in the Gnome Keyring.
2002 - A new EAP-GTC plugin implements draft-sheffer-ikev2-gtc-00.txt and allows
2003 username/password authentication against any PAM service on the gateway.
2004 The new EAP method interacts nicely with the NetworkManager plugin and allows
2005 client authentication against e.g. LDAP.
2007 - Improved support for the EAP-Identity method. The new ipsec.conf eap_identity
2008 parameter defines an additional identity to pass to the server in EAP
2011 - The "ipsec statusall" command now lists CA restrictions, EAP
2012 authentication types and EAP identities.
2014 - Fixed two multithreading deadlocks occurring when starting up
2015 several hundred tunnels concurrently.
2017 - Fixed the --enable-integrity-test configure option which
2018 computes a SHA-1 checksum over the libstrongswan library.
2024 - Consistent logging of IKE and CHILD SAs at the audit (AUD) level.
2026 - Improved the performance of the SQL-based virtual IP address pool
2027 by introducing an additional addresses table. The leases table
2028 storing only history information has become optional and can be
2029 disabled by setting charon.plugins.sql.lease_history = no in
2032 - The XFRM_STATE_AF_UNSPEC flag added to xfrm.h allows IPv4-over-IPv6
2033 and IPv6-over-IPv4 tunnels with the 2.6.26 and later Linux kernels.
2035 - management of different virtual IP pools for different
2036 network interfaces have become possible.
2038 - fixed a bug which prevented the assignment of more than 256
2039 virtual IP addresses from a pool managed by an sql database.
2041 - fixed a bug which did not delete own IPCOMP SAs in the kernel.
2047 - Added statistics functions to ipsec pool --status and ipsec pool --leases
2048 and input validation checks to various ipsec pool commands.
2050 - ipsec statusall now lists all loaded charon plugins and displays
2051 the negotiated IKEv2 cipher suite proposals.
2053 - The openssl plugin supports the elliptic curve Diffie-Hellman groups
2054 19, 20, 21, 25, and 26.
2056 - The openssl plugin supports ECDSA authentication using elliptic curve
2059 - Fixed a bug in stroke which caused multiple charon threads to close
2060 the file descriptors during packet transfers over the stroke socket.
2062 - ESP sequence numbers are now migrated in IPsec SA updates handled by
2063 MOBIKE. Works only with Linux kernels >= 2.6.17.
2069 - Fixed the strongswan.conf path configuration problem that occurred when
2070 --sysconfig was not set explicitly in ./configure.
2072 - Fixed a number of minor bugs that where discovered during the 4th
2073 IKEv2 interoperability workshop in San Antonio, TX.
2079 - Plugins for libstrongswan and charon can optionally be loaded according
2080 to a configuration in strongswan.conf. Most components provide a
2081 "load = " option followed by a space separated list of plugins to load.
2082 This allows e.g. the fallback from a hardware crypto accelerator to
2083 to software-based crypto plugins.
2085 - Charons SQL plugin has been extended by a virtual IP address pool.
2086 Configurations with a rightsourceip=%poolname setting query a SQLite or
2087 MySQL database for leases. The "ipsec pool" command helps in administrating
2088 the pool database. See ipsec pool --help for the available options
2090 - The Authenticated Encryption Algorithms AES-CCM-8/12/16 and AES-GCM-8/12/16
2091 for ESP are now supported starting with the Linux 2.6.25 kernel. The
2092 syntax is e.g. esp=aes128ccm12 or esp=aes256gcm16.
2098 - Support for "Hash and URL" encoded certificate payloads has been implemented
2099 in the IKEv2 daemon charon. Using the "certuribase" option of a CA section
2100 allows to assign a base URL to all certificates issued by the specified CA.
2101 The final URL is then built by concatenating that base and the hex encoded
2102 SHA1 hash of the DER encoded certificate. Note that this feature is disabled
2103 by default and must be enabled using the option "charon.hash_and_url".
2105 - The IKEv2 daemon charon now supports the "uniqueids" option to close multiple
2106 IKE_SAs with the same peer. The option value "keep" prefers existing
2107 connection setups over new ones, where the value "replace" replaces existing
2110 - The crypto factory in libstrongswan additionally supports random number
2111 generators, plugins may provide other sources of randomness. The default
2112 plugin reads raw random data from /dev/(u)random.
2114 - Extended the credential framework by a caching option to allow plugins
2115 persistent caching of fetched credentials. The "cachecrl" option has been
2118 - The new trustchain verification introduced in 4.2.0 has been parallelized.
2119 Threads fetching CRL or OCSP information no longer block other threads.
2121 - A new IKEv2 configuration attribute framework has been introduced allowing
2122 plugins to provide virtual IP addresses, and in the future, other
2123 configuration attribute services (e.g. DNS/WINS servers).
2125 - The stroke plugin has been extended to provide virtual IP addresses from
2126 a pool defined in ipsec.conf. The "rightsourceip" parameter now accepts
2127 address pools in CIDR notation (e.g. 10.1.1.0/24). The parameter also accepts
2128 the value "%poolname", where "poolname" identifies a pool provided by a
2131 - Fixed compilation on uClibc and a couple of other minor bugs.
2133 - Set DPD defaults in ipsec starter to dpd_delay=30s and dpd_timeout=150s.
2135 - The IKEv1 pluto daemon now supports the ESP encryption algorithm CAMELLIA
2136 with key lengths of 128, 192, and 256 bits, as well as the authentication
2137 algorithm AES_XCBC_MAC. Configuration example: esp=camellia192-aesxcbc.
2143 - libstrongswan has been modularized to attach crypto algorithms,
2144 credential implementations (keys, certificates) and fetchers dynamically
2145 through plugins. Existing code has been ported to plugins:
2146 - RSA/Diffie-Hellman implementation using the GNU Multi Precision library
2147 - X509 certificate system supporting CRLs, OCSP and attribute certificates
2148 - Multiple plugins providing crypto algorithms in software
2149 - CURL and OpenLDAP fetcher
2151 - libstrongswan gained a relational database API which uses pluggable database
2152 providers. Plugins for MySQL and SQLite are available.
2154 - The IKEv2 keying daemon charon is more extensible. Generic plugins may provide
2155 connection configuration, credentials and EAP methods or control the daemon.
2156 Existing code has been ported to plugins:
2157 - EAP-AKA, EAP-SIM, EAP-MD5 and EAP-Identity
2158 - stroke configuration, credential and control (compatible to pluto)
2159 - XML bases management protocol to control and query the daemon
2160 The following new plugins are available:
2161 - An experimental SQL configuration, credential and logging plugin on
2162 top of either MySQL or SQLite
2163 - A unit testing plugin to run tests at daemon startup
2165 - The authentication and credential framework in charon has been heavily
2166 refactored to support modular credential providers, proper
2167 CERTREQ/CERT payload exchanges and extensible authorization rules.
2169 - The framework of strongSwan Manager has evolved to the web application
2170 framework libfast (FastCGI Application Server w/ Templates) and is usable
2171 by other applications.
2177 - IKE rekeying in NAT situations did not inherit the NAT conditions
2178 to the rekeyed IKE_SA so that the UDP encapsulation was lost with
2179 the next CHILD_SA rekeying.
2181 - Wrong type definition of the next_payload variable in id_payload.c
2182 caused an INVALID_SYNTAX error on PowerPC platforms.
2184 - Implemented IKEv2 EAP-SIM server and client test modules that use
2185 triplets stored in a file. For details on the configuration see
2186 the scenario 'ikev2/rw-eap-sim-rsa'.
2192 - Fixed error in the ordering of the certinfo_t records in the ocsp cache that
2193 caused multiple entries of the same serial number to be created.
2195 - Implementation of a simple EAP-MD5 module which provides CHAP
2196 authentication. This may be interesting in conjunction with certificate
2197 based server authentication, as weak passwords can't be brute forced
2198 (in contradiction to traditional IKEv2 PSK).
2200 - A complete software based implementation of EAP-AKA, using algorithms
2201 specified in 3GPP2 (S.S0055). This implementation does not use an USIM,
2202 but reads the secrets from ipsec.secrets. Make sure to read eap_aka.h
2205 - Support for vendor specific EAP methods using Expanded EAP types. The
2206 interface to EAP modules has been slightly changed, so make sure to
2207 check the changes if you're already rolling your own modules.
2213 - The default _updown script now dynamically inserts and removes ip6tables
2214 firewall rules if leftfirewall=yes is set in IPv6 connections. New IPv6
2215 net-net and roadwarrior (PSK/RSA) scenarios for both IKEv1 and IKEV2 were
2218 - Implemented RFC4478 repeated authentication to force EAP/Virtual-IP clients
2219 to reestablish an IKE_SA within a given timeframe.
2221 - strongSwan Manager supports configuration listing, initiation and termination
2222 of IKE and CHILD_SAs.
2224 - Fixes and improvements to multithreading code.
2226 - IKEv2 plugins have been renamed to libcharon-* to avoid naming conflicts.
2227 Make sure to remove the old plugins in $libexecdir/ipsec, otherwise they get
2234 - Removed recursive pthread mutexes since uClibc doesn't support them.
2240 - In NAT traversal situations and multiple queued Quick Modes,
2241 those pending connections inserted by auto=start after the
2242 port floating from 500 to 4500 were erroneously deleted.
2244 - Added a "forceencaps" connection parameter to enforce UDP encapsulation
2245 to surmount restrictive firewalls. NAT detection payloads are faked to
2246 simulate a NAT situation and trick the other peer into NAT mode (IKEv2 only).
2248 - Preview of strongSwan Manager, a web based configuration and monitoring
2249 application. It uses a new XML control interface to query the IKEv2 daemon
2250 (see http://wiki.strongswan.org/wiki/Manager).
2252 - Experimental SQLite configuration backend which will provide the configuration
2253 interface for strongSwan Manager in future releases.
2255 - Further improvements to MOBIKE support.
2261 - Since some third party IKEv2 implementations run into
2262 problems with strongSwan announcing MOBIKE capability per
2263 default, MOBIKE can be disabled on a per-connection-basis
2264 using the mobike=no option. Whereas mobike=no disables the
2265 sending of the MOBIKE_SUPPORTED notification and the floating
2266 to UDP port 4500 with the IKE_AUTH request even if no NAT
2267 situation has been detected, strongSwan will still support
2268 MOBIKE acting as a responder.
2270 - the default ipsec routing table plus its corresponding priority
2271 used for inserting source routes has been changed from 100 to 220.
2272 It can be configured using the --with-ipsec-routing-table and
2273 --with-ipsec-routing-table-prio options.
2275 - the --enable-integrity-test configure option tests the
2276 integrity of the libstrongswan crypto code during the charon
2279 - the --disable-xauth-vid configure option disables the sending
2280 of the XAUTH vendor ID. This can be used as a workaround when
2281 interoperating with some Windows VPN clients that get into
2282 trouble upon reception of an XAUTH VID without eXtended
2283 AUTHentication having been configured.
2285 - ipsec stroke now supports the rereadsecrets, rereadaacerts,
2286 rereadacerts, and listacerts options.
2292 - If a DNS lookup failure occurs when resolving right=%<FQDN>
2293 or right=<FQDN> combined with rightallowany=yes then the
2294 connection is not updated by ipsec starter thus preventing
2295 the disruption of an active IPsec connection. Only if the DNS
2296 lookup successfully returns with a changed IP address the
2297 corresponding connection definition is updated.
2299 - Routes installed by the keying daemons are now in a separate
2300 routing table with the ID 100 to avoid conflicts with the main
2301 table. Route lookup for IKEv2 traffic is done in userspace to ignore
2302 routes installed for IPsec, as IKE traffic shouldn't get encapsulated.
2308 - The pluto IKEv1 daemon now exhibits the same behaviour as its
2309 IKEv2 companion charon by inserting an explicit route via the
2310 _updown script only if a sourceip exists. This is admissible
2311 since routing through the IPsec tunnel is handled automatically
2312 by NETKEY's IPsec policies. As a consequence the left|rightnexthop
2313 parameter is not required any more.
2315 - The new IKEv1 parameter right|leftallowany parameters helps to handle
2316 the case where both peers possess dynamic IP addresses that are
2317 usually resolved using DynDNS or a similar service. The configuration
2322 can be used by the initiator to start up a connection to a peer
2323 by resolving peer.foo.bar into the currently allocated IP address.
2324 Thanks to the rightallowany flag the connection behaves later on
2329 so that the peer can rekey the connection as an initiator when his
2330 IP address changes. An alternative notation is
2334 which will implicitly set rightallowany=yes.
2336 - ipsec starter now fails more gracefully in the presence of parsing
2337 errors. Flawed ca and conn section are discarded and pluto is started
2338 if non-fatal errors only were encountered. If right=%peer.foo.bar
2339 cannot be resolved by DNS then right=%any will be used so that passive
2340 connections as a responder are still possible.
2342 - The new pkcs11initargs parameter that can be placed in the
2343 setup config section of /etc/ipsec.conf allows the definition
2344 of an argument string that is used with the PKCS#11 C_Initialize()
2345 function. This non-standard feature is required by the NSS softoken
2346 library. This patch was contributed by Robert Varga.
2348 - Fixed a bug in ipsec starter introduced by strongswan-2.8.5
2349 which caused a segmentation fault in the presence of unknown
2350 or misspelt keywords in ipsec.conf. This bug fix was contributed
2353 - Partial support for MOBIKE in IKEv2. The initiator acts on interface/
2354 address configuration changes and updates IKE and IPsec SAs dynamically.
2360 - IKEv2 peer configuration selection now can be based on a given
2361 certification authority using the rightca= statement.
2363 - IKEv2 authentication based on RSA signatures now can handle multiple
2364 certificates issued for a given peer ID. This allows a smooth transition
2365 in the case of a peer certificate renewal.
2367 - IKEv2: Support for requesting a specific virtual IP using leftsourceip on the
2368 client and returning requested virtual IPs using rightsourceip=%config
2369 on the server. If the server does not support configuration payloads, the
2370 client enforces its leftsourceip parameter.
2372 - The ./configure options --with-uid/--with-gid allow pluto and charon
2373 to drop their privileges to a minimum and change to an other UID/GID. This
2374 improves the systems security, as a possible intruder may only get the
2375 CAP_NET_ADMIN capability.
2377 - Further modularization of charon: Pluggable control interface and
2378 configuration backend modules provide extensibility. The control interface
2379 for stroke is included, and further interfaces using DBUS (NetworkManager)
2380 or XML are on the way. A backend for storing configurations in the daemon
2381 is provided and more advanced backends (using e.g. a database) are trivial
2384 - Fixed a compilation failure in libfreeswan occurring with Linux kernel
2391 - Support for an additional Diffie-Hellman exchange when creating/rekeying
2392 a CHILD_SA in IKEv2 (PFS). PFS is enabled when the proposal contains a
2393 DH group (e.g. "esp=aes128-sha1-modp1536"). Further, DH group negotiation
2394 is implemented properly for rekeying.
2396 - Support for the AES-XCBC-96 MAC algorithm for IPsec SAs when using IKEv2
2397 (requires linux >= 2.6.20). It is enabled using e.g. "esp=aes256-aesxcbc".
2399 - Working IPv4-in-IPv6 and IPv6-in-IPv4 tunnels for linux >= 2.6.21.
2401 - Added support for EAP modules which do not establish an MSK.
2403 - Removed the dependencies from the /usr/include/linux/ headers by
2404 including xfrm.h, ipsec.h, and pfkeyv2.h in the distribution.
2406 - crlNumber is now listed by ipsec listcrls
2408 - The xauth_modules.verify_secret() function now passes the
2415 - Server side cookie support. If to may IKE_SAs are in CONNECTING state,
2416 cookies are enabled and protect against DoS attacks with faked source
2417 addresses. Number of IKE_SAs in CONNECTING state is also limited per
2418 peer address to avoid resource exhaustion. IKE_SA_INIT messages are
2419 compared to properly detect retransmissions and incoming retransmits are
2420 detected even if the IKE_SA is blocked (e.g. doing OCSP fetches).
2422 - The IKEv2 daemon charon now supports dynamic http- and ldap-based CRL
2423 fetching enabled by crlcheckinterval > 0 and caching fetched CRLs
2424 enabled by cachecrls=yes.
2426 - Added the configuration options --enable-nat-transport which enables
2427 the potentially insecure NAT traversal for IPsec transport mode and
2428 --disable-vendor-id which disables the sending of the strongSwan
2431 - Fixed a long-standing bug in the pluto IKEv1 daemon which caused
2432 a segmentation fault if a malformed payload was detected in the
2433 IKE MR2 message and pluto tried to send an encrypted notification
2436 - Added the NATT_IETF_02_N Vendor ID in order to support IKEv1 connections
2437 with Windows 2003 Server which uses a wrong VID hash.
2443 - Support of SHA2_384 hash function for protecting IKEv1
2444 negotiations and support of SHA2 signatures in X.509 certificates.
2446 - Fixed a serious bug in the computation of the SHA2-512 HMAC
2447 function. Introduced automatic self-test of all IKEv1 hash
2448 and hmac functions during pluto startup. Failure of a self-test
2449 currently issues a warning only but does not exit pluto [yet].
2451 - Support for SHA2-256/384/512 PRF and HMAC functions in IKEv2.
2453 - Full support of CA information sections. ipsec listcainfos
2454 now shows all collected crlDistributionPoints and OCSP
2457 - Support of the Online Certificate Status Protocol (OCSP) for IKEv2.
2458 This feature requires the HTTP fetching capabilities of the libcurl
2459 library which must be enabled by setting the --enable-http configure
2462 - Refactored core of the IKEv2 message processing code, allowing better
2463 code reuse and separation.
2465 - Virtual IP support in IKEv2 using INTERNAL_IP4/6_ADDRESS configuration
2466 payload. Additionally, the INTERNAL_IP4/6_DNS attribute is interpreted
2467 by the requestor and installed in a resolv.conf file.
2469 - The IKEv2 daemon charon installs a route for each IPsec policy to use
2470 the correct source address even if an application does not explicitly
2473 - Integrated the EAP framework into charon which loads pluggable EAP library
2474 modules. The ipsec.conf parameter authby=eap initiates EAP authentication
2475 on the client side, while the "eap" parameter on the server side defines
2476 the EAP method to use for client authentication.
2477 A generic client side EAP-Identity module and an EAP-SIM authentication
2478 module using a third party card reader implementation are included.
2480 - Added client side support for cookies.
2482 - Integrated the fixes done at the IKEv2 interoperability bakeoff, including
2483 strict payload order, correct INVALID_KE_PAYLOAD rejection and other minor
2484 fixes to enhance interoperability with other implementations.
2490 - strongSwan now interoperates with the NCP Secure Entry Client,
2491 the Shrew Soft VPN Client, and the Cisco VPN client, doing both
2492 XAUTH and Mode Config.
2494 - UNITY attributes are now recognized and UNITY_BANNER is set
2495 to a default string.
2501 - IKEv1: Support for extended authentication (XAUTH) in combination
2502 with ISAKMP Main Mode RSA or PSK authentication. Both client and
2503 server side were implemented. Handling of user credentials can
2504 be done by a run-time loadable XAUTH module. By default user
2505 credentials are stored in ipsec.secrets.
2507 - IKEv2: Support for reauthentication when rekeying
2509 - IKEv2: Support for transport mode
2511 - fixed a lot of bugs related to byte order
2513 - various other bugfixes
2519 - IKEv1: Implementation of ModeConfig push mode via the new connection
2520 keyword modeconfig=push allows interoperability with Cisco VPN gateways.
2522 - IKEv1: The command ipsec statusall now shows "DPD active" for all
2523 ISAKMP SAs that are under active Dead Peer Detection control.
2525 - IKEv2: Charon's logging and debugging framework has been completely rewritten.
2526 Instead of logger, special printf() functions are used to directly
2527 print objects like hosts (%H) identifications (%D), certificates (%Q),
2528 etc. The number of debugging levels have been reduced to:
2530 0 (audit), 1 (control), 2 (controlmore), 3 (raw), 4 (private)
2532 The debugging levels can either be specified statically in ipsec.conf as
2535 charondebug="lib 1, cfg 3, net 2"
2537 or changed at runtime via stroke as
2539 ipsec stroke loglevel cfg 2
2545 - Implemented full support for IPv6-in-IPv6 tunnels.
2547 - Added configuration options for dead peer detection in IKEv2. dpd_action
2548 types "clear", "hold" and "restart" are supported. The dpd_timeout
2549 value is not used, as the normal retransmission policy applies to
2550 detect dead peers. The dpd_delay parameter enables sending of empty
2551 informational message to detect dead peers in case of inactivity.
2553 - Added support for preshared keys in IKEv2. PSK keys configured in
2554 ipsec.secrets are loaded. The authby parameter specifies the authentication
2555 method to authentificate ourself, the other peer may use PSK or RSA.
2557 - Changed retransmission policy to respect the keyingtries parameter.
2559 - Added private key decryption. PEM keys encrypted with AES-128/192/256
2560 or 3DES are supported.
2562 - Implemented DES/3DES algorithms in libstrongswan. 3DES can be used to
2563 encrypt IKE traffic.
2565 - Implemented SHA-256/384/512 in libstrongswan, allows usage of certificates
2566 signed with such a hash algorithm.
2568 - Added initial support for updown scripts. The actions up-host/client and
2569 down-host/client are executed. The leftfirewall=yes parameter
2570 uses the default updown script to insert dynamic firewall rules, a custom
2571 updown script may be specified with the leftupdown parameter.
2577 - Added support for the auto=route ipsec.conf parameter and the
2578 ipsec route/unroute commands for IKEv2. This allows to set up IKE_SAs and
2579 CHILD_SAs dynamically on demand when traffic is detected by the
2582 - Added support for rekeying IKE_SAs in IKEv2 using the ikelifetime parameter.
2583 As specified in IKEv2, no reauthentication is done (unlike in IKEv1), only
2584 new keys are generated using perfect forward secrecy. An optional flag
2585 which enforces reauthentication will be implemented later.
2587 - "sha" and "sha1" are now treated as synonyms in the ike= and esp=
2588 algorithm configuration statements.
2594 - Full X.509 certificate trust chain verification has been implemented.
2595 End entity certificates can be exchanged via CERT payloads. The current
2596 default is leftsendcert=always, since CERTREQ payloads are not supported
2597 yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls.
2599 - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2
2600 would offer more possibilities for traffic selection, but the Linux kernel
2601 currently does not support it. That's why we stick with these simple
2602 ipsec.conf rules for now.
2604 - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no
2605 IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear,
2608 - Initial NAT traversal support in IKEv2. Charon includes NAT detection
2609 notify payloads to detect NAT routers between the peers. It switches
2610 to port 4500, uses UDP encapsulated ESP packets, handles peer address
2611 changes gracefully and sends keep alive message periodically.
2613 - Reimplemented IKE_SA state machine for charon, which allows simultaneous
2614 rekeying, more shared code, cleaner design, proper retransmission
2615 and a more extensible code base.
2617 - The mixed PSK/RSA roadwarrior detection capability introduced by the
2618 strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal
2619 payloads by the responder right before any defined IKE Main Mode state had
2620 been established. Although any form of bad proposal syntax was being correctly
2621 detected by the payload parser, the subsequent error handler didn't check
2622 the state pointer before logging current state information, causing an
2623 immediate crash of the pluto keying daemon due to a NULL pointer.
2629 - Added algorithm selection to charon: New default algorithms for
2630 ike=aes128-sha-modp2048, as both daemons support it. The default
2631 for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles
2632 the ike/esp parameter the same way as pluto. As this syntax does
2633 not allow specification of a pseudo random function, the same
2634 algorithm as for integrity is used (currently sha/md5). Supported
2636 Encryption: aes128, aes192, aes256
2637 Integrity/PRF: md5, sha (using hmac)
2638 DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192
2640 Encryption: aes128, aes192, aes256, 3des, blowfish128,
2641 blowfish192, blowfish256
2642 Integrity: md5, sha1
2643 More IKE encryption algorithms will come after porting libcrypto into
2646 - initial support for rekeying CHILD_SAs using IKEv2. Currently no
2647 perfect forward secrecy is used. The rekeying parameters rekey,
2648 rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported
2649 when using IKEv2. WARNING: charon currently is unable to handle
2650 simultaneous rekeying. To avoid such a situation, use a large
2651 rekeyfuzz, or even better, set rekey=no on one peer.
2653 - support for host2host, net2net, host2net (roadwarrior) tunnels
2654 using predefined RSA certificates (see uml scenarios for
2655 configuration examples).
2657 - new build environment featuring autotools. Features such
2658 as HTTP, LDAP and smartcard support may be enabled using
2659 the ./configure script. Changing install directories
2660 is possible, too. See ./configure --help for more details.
2662 - better integration of charon with ipsec starter, which allows
2663 (almost) transparent operation with both daemons. charon
2664 handles ipsec commands up, down, status, statusall, listall,
2665 listcerts and allows proper load, reload and delete of connections
2672 - initial support of the IKEv2 protocol. Connections in
2673 ipsec.conf designated by keyexchange=ikev2 are negotiated
2674 by the new IKEv2 charon keying daemon whereas those marked
2675 by keyexchange=ikev1 or the default keyexchange=ike are
2676 handled thy the IKEv1 pluto keying daemon. Currently only
2677 a limited subset of functions are available with IKEv2
2678 (Default AES encryption, authentication based on locally
2679 imported X.509 certificates, unencrypted private RSA keys
2680 in PKCS#1 file format, limited functionality of the ipsec
2687 - the dynamic iptables rules from the _updown_x509 template
2688 for KLIPS and the _updown_policy template for NETKEY have
2689 been merged into the default _updown script. The existing
2690 left|rightfirewall keyword causes the automatic insertion
2691 and deletion of ACCEPT rules for tunneled traffic upon
2692 the successful setup and teardown of an IPsec SA, respectively.
2693 left|rightfirwall can be used with KLIPS under any Linux 2.4
2694 kernel or with NETKEY under a Linux kernel version >= 2.6.16
2695 in conjunction with iptables >= 1.3.5. For NETKEY under a Linux
2696 kernel version < 2.6.16 which does not support IPsec policy
2697 matching yet, please continue to use a copy of the _updown_espmark
2698 template loaded via the left|rightupdown keyword.
2700 - a new left|righthostaccess keyword has been introduced which
2701 can be used in conjunction with left|rightfirewall and the
2702 default _updown script. By default leftfirewall=yes inserts
2703 a bi-directional iptables FORWARD rule for a local client network
2704 with a netmask different from 255.255.255.255 (single host).
2705 This does not allow to access the VPN gateway host via its
2706 internal network interface which is part of the client subnet
2707 because an iptables INPUT and OUTPUT rule would be required.
2708 lefthostaccess=yes will cause this additional ACCEPT rules to
2711 - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal
2712 payload is preparsed in order to find out whether the roadwarrior
2713 requests PSK or RSA so that a matching connection candidate can
2720 - the new _updown_policy template allows ipsec policy based
2721 iptables firewall rules. Required are iptables version
2722 >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes
2723 the _updown_espmark template, so that no INPUT mangle rules
2724 are required any more.
2726 - added support of DPD restart mode
2728 - ipsec starter now allows the use of wildcards in include
2729 statements as e.g. in "include /etc/my_ipsec/*.conf".
2730 Patch courtesy of Matthias Haas.
2732 - the Netscape OID 'employeeNumber' is now recognized and can be
2733 used as a Relative Distinguished Name in certificates.
2739 - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec
2740 command and not of ipsec setup any more.
2742 - ipsec starter now supports AH authentication in conjunction with
2743 ESP encryption. AH authentication is configured in ipsec.conf
2744 via the auth=ah parameter.
2746 - The command ipsec scencrypt|scdecrypt <args> is now an alias for
2747 ipsec whack --scencrypt|scdecrypt <args>.
2749 - get_sa_info() now determines for the native netkey IPsec stack
2750 the exact time of the last use of an active eroute. This information
2751 is used by the Dead Peer Detection algorithm and is also displayed by
2752 the ipsec status command.
2758 - running under the native Linux 2.6 IPsec stack, the function
2759 get_sa_info() is called by ipsec auto --status to display the current
2760 number of transmitted bytes per IPsec SA.
2762 - get_sa_info() is also used by the Dead Peer Detection process to detect
2763 recent ESP activity. If ESP traffic was received from the peer within
2764 the last dpd_delay interval then no R_Y_THERE notification must be sent.
2766 - strongSwan now supports the Relative Distinguished Name "unstructuredName"
2767 in ID_DER_ASN1_DN identities. The following notations are possible:
2769 rightid="unstructuredName=John Doe"
2770 rightid="UN=John Doe"
2772 - fixed a long-standing bug which caused PSK-based roadwarrior connections
2773 to segfault in the function id.c:same_id() called by keys.c:get_secret()
2774 if an FQDN, USER_FQDN, or Key ID was defined, as in the following example.
2781 - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall).
2783 - ipsec starter didn't set host_addr and client.addr ports in whack msg.
2785 - in order to guarantee backwards-compatibility with the script-based
2786 auto function (e.g. auto --replace), the ipsec starter scripts stores
2787 the defaultroute information in the temporary file /var/run/ipsec.info.
2789 - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH
2790 Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config
2793 - the ipsec starter now also recognizes the parameters authby=never and
2794 type=passthrough|pass|drop|reject.
2800 - ipsec starter now supports the also parameter which allows
2801 a modular structure of the connection definitions. Thus
2802 "ipsec start" is now ready to replace "ipsec setup".
2808 - Mathieu Lafon's popular ipsec starter tool has been added to the
2809 strongSwan distribution. Many thanks go to Stephan Scholz from astaro
2810 for his integration work. ipsec starter is a C program which is going
2811 to replace the various shell and awk starter scripts (setup, _plutoload,
2812 _plutostart, _realsetup, _startklips, _confread, and auto). Since
2813 ipsec.conf is now parsed only once, the starting of multiple tunnels is
2814 accelerated tremedously.
2816 - Added support of %defaultroute to the ipsec starter. If the IP address
2817 changes, a HUP signal to the ipsec starter will automatically
2818 reload pluto's connections.
2820 - moved most compile time configurations from pluto/Makefile to
2821 Makefile.inc by defining the options USE_LIBCURL, USE_LDAP,
2822 USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE.
2824 - removed the ipsec verify and ipsec newhostkey commands
2826 - fixed some 64-bit issues in formatted print statements
2828 - The scepclient functionality implementing the Simple Certificate
2829 Enrollment Protocol (SCEP) is nearly complete but hasn't been
2836 - CA certificates are now automatically loaded from a smartcard
2837 or USB crypto token and appear in the ipsec auto --listcacerts
2844 - when using "ipsec whack --scencrypt <data>" with a PKCS#11
2845 library that does not support the C_Encrypt() Cryptoki
2846 function (e.g. OpenSC), the RSA encryption is done in
2847 software using the public key fetched from the smartcard.
2849 - The scepclient function now allows to define the
2850 validity of a self-signed certificate using the --days,
2851 --startdate, and --enddate options. The default validity
2852 has been changed from one year to five years.
2858 - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11
2859 interface to other applications for RSA encryption and decryption
2860 via the whack interface. Notation:
2862 ipsec whack --scencrypt <data>
2863 [--inbase 16|hex|64|base64|256|text|ascii]
2864 [--outbase 16|hex|64|base64|256|text|ascii]
2867 ipsec whack --scdecrypt <data>
2868 [--inbase 16|hex|64|base64|256|text|ascii]
2869 [--outbase 16|hex|64|base64|256|text|ascii]
2872 The default setting for inbase and outbase is hex.
2874 The new proxy interface can be used for securing symmetric
2875 encryption keys required by the cryptoloop or dm-crypt
2876 disk encryption schemes, especially in the case when
2877 pkcs11keepstate=yes causes pluto to lock the pkcs11 slot
2880 - if the file /etc/ipsec.secrets is lacking during the startup of
2881 pluto then the root-readable file /etc/ipsec.d/private/myKey.der
2882 containing a 2048 bit RSA private key and a matching self-signed
2883 certificate stored in the file /etc/ipsec.d/certs/selfCert.der
2884 is automatically generated by calling the function
2886 ipsec scepclient --out pkcs1 --out cert-self
2888 scepclient was written by Jan Hutter and Martin Willi, students
2889 at the University of Applied Sciences in Rapperswil, Switzerland.
2895 - the current extension of the PKCS#7 framework introduced
2896 a parsing error in PKCS#7 wrapped X.509 certificates that are
2897 e.g. transmitted by Windows XP when multi-level CAs are used.
2898 the parsing syntax has been fixed.
2900 - added a patch by Gerald Richter which tolerates multiple occurrences
2901 of the ipsec0 interface when using KLIPS.
2907 - with gawk-3.1.4 the word "default2 has become a protected
2908 keyword for use in switch statements and cannot be used any
2909 more in the strongSwan scripts. This problem has been
2910 solved by renaming "default" to "defaults" and "setdefault"
2911 in the scripts _confread and auto, respectively.
2913 - introduced the parameter leftsendcert with the values
2915 always|yes (the default, always send a cert)
2916 ifasked (send the cert only upon a cert request)
2917 never|no (never send a cert, used for raw RSA keys and
2920 - fixed the initialization of the ESP key length to a default of
2921 128 bits in the case that the peer does not send a key length
2922 attribute for AES encryption.
2924 - applied Herbert Xu's uniqueIDs patch
2926 - applied Herbert Xu's CLOEXEC patches
2932 - CRLs can now be cached also in the case when the issuer's
2933 certificate does not contain a subjectKeyIdentifier field.
2934 In that case the subjectKeyIdentifier is computed by pluto as the
2935 160 bit SHA-1 hash of the issuer's public key in compliance
2936 with section 4.2.1.2 of RFC 3280.
2938 - Fixed a bug introduced by strongswan-2.5.1 which eliminated
2939 not only multiple Quick Modes of a given connection but also
2940 multiple connections between two security gateways.
2946 - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute
2947 installed either by setting auto=route in ipsec.conf or by
2948 a connection put into hold, generates an XFRM_AQUIRE event
2949 for each packet that wants to use the not-yet existing
2950 tunnel. Up to now each XFRM_AQUIRE event led to an entry in
2951 the Quick Mode queue, causing multiple IPsec SA to be
2952 established in rapid succession. Starting with strongswan-2.5.1
2953 only a single IPsec SA is established per host-pair connection.
2955 - Right after loading the PKCS#11 module, all smartcard slots are
2956 searched for certificates. The result can be viewed using
2959 ipsec auto --listcards
2961 The certificate objects found in the slots are numbered
2962 starting with #1, #2, etc. This position number can be used to address
2963 certificates (leftcert=%smartcard) and keys (: PIN %smartcard)
2964 in ipsec.conf and ipsec.secrets, respectively:
2966 %smartcard (selects object #1)
2967 %smartcard#1 (selects object #1)
2968 %smartcard#3 (selects object #3)
2970 As an alternative the existing retrieval scheme can be used:
2972 %smartcard:45 (selects object with id=45)
2973 %smartcard0 (selects first object in slot 0)
2974 %smartcard4:45 (selects object in slot 4 with id=45)
2976 - Depending on the settings of CKA_SIGN and CKA_DECRYPT
2977 private key flags either C_Sign() or C_Decrypt() is used
2978 to generate a signature.
2980 - The output buffer length parameter siglen in C_Sign()
2981 is now initialized to the actual size of the output
2982 buffer prior to the function call. This fixes the
2983 CKR_BUFFER_TOO_SMALL error that could occur when using
2984 the OpenSC PKCS#11 module.
2986 - Changed the initialization of the PKCS#11 CK_MECHANISM in
2987 C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }.
2989 - Refactored the RSA public/private key code and transferred it
2990 from keys.c to the new pkcs1.c file as a preparatory step
2991 towards the release of the SCEP client.
2997 - The loading of a PKCS#11 smartcard library module during
2998 runtime does not require OpenSC library functions any more
2999 because the corresponding code has been integrated into
3000 smartcard.c. Also the RSAREF pkcs11 header files have been
3001 included in a newly created pluto/rsaref directory so that
3002 no external include path has to be defined any longer.
3004 - A long-awaited feature has been implemented at last:
3005 The local caching of CRLs fetched via HTTP or LDAP, activated
3006 by the parameter cachecrls=yes in the config setup section
3007 of ipsec.conf. The dynamically fetched CRLs are stored under
3008 a unique file name containing the issuer's subjectKeyID
3009 in /etc/ipsec.d/crls.
3011 - Applied a one-line patch courtesy of Michael Richardson
3012 from the Openswan project which fixes the kernel-oops
3013 in KLIPS when an snmp daemon is running on the same box.
3019 - Eliminated null length CRL distribution point strings.
3021 - Fixed a trust path evaluation bug introduced with 2.4.3
3027 - Improved the joint OCSP / CRL revocation policy.
3028 OCSP responses have precedence over CRL entries.
3030 - Introduced support of CRLv2 reason codes.
3032 - Fixed a bug with key-pad equipped readers which caused
3033 pluto to prompt for the pin via the console when the first
3034 occasion to enter the pin via the key-pad was missed.
3036 - When pluto is built with LDAP_V3 enabled, the library
3037 liblber required by newer versions of openldap is now
3044 - Added the _updown_espmark template which requires all
3045 incoming ESP traffic to be marked with a default mark
3048 - Introduced the pkcs11keepstate parameter in the config setup
3049 section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11
3050 session and login states are kept as long as possible during
3051 the lifetime of pluto. This means that a PIN entry via a key
3052 pad has to be done only once.
3054 - Introduced the pkcs11module parameter in the config setup
3055 section of ipsec.conf which specifies the PKCS#11 module
3056 to be used with smart cards. Example:
3058 pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo
3060 - Added support of smartcard readers equipped with a PIN pad.
3062 - Added patch by Jay Pfeifer which detects when netkey
3063 modules have been statically built into the Linux 2.6 kernel.
3065 - Added two patches by Herbert Xu. The first uses ip xfrm
3066 instead of setkey to flush the IPsec policy database. The
3067 second sets the optional flag in inbound IPComp SAs only.
3069 - Applied Ulrich Weber's patch which fixes an interoperability
3070 problem between native IPsec and KLIPS systems caused by
3071 setting the replay window to 32 instead of 0 for ipcomp.
3077 - Fixed a bug which caused an unwanted Mode Config request
3078 to be initiated in the case where "right" was used to denote
3079 the local side in ipsec.conf and "left" the remote side,
3080 contrary to the recommendation that "right" be remote and
3087 - updated Vendor ID to strongSwan-2.4.0
3089 - updated copyright statement to include David Buechi and
3096 - strongSwan now communicates with attached smartcards and
3097 USB crypto tokens via the standardized PKCS #11 interface.
3098 By default the OpenSC library from www.opensc.org is used
3099 but any other PKCS#11 library could be dynamically linked.
3100 strongSwan's PKCS#11 API was implemented by David Buechi
3101 and Michael Meier, both graduates of the Zurich University
3102 of Applied Sciences in Winterthur, Switzerland.
3104 - When a %trap eroute is triggered by an outgoing IP packet
3105 then the native IPsec stack of the Linux 2.6 kernel [often/
3106 always?] returns an XFRM_ACQUIRE message with an undefined
3107 protocol family field and the connection setup fails.
3108 As a workaround IPv4 (AF_INET) is now assumed.
3110 - the results of the UML test scenarios are now enhanced
3111 with block diagrams of the virtual network topology used
3112 in a particular test.
3118 - fixed IV used to decrypt informational messages.
3119 This bug was introduced with Mode Config functionality.
3121 - fixed NCP Vendor ID.
3123 - undid one of Ulrich Weber's maximum udp size patches
3124 because it caused a segmentation fault with NAT-ed
3127 - added UML scenarios wildcards and attr-cert which
3128 demonstrate the implementation of IPsec policies based
3129 on wildcard parameters contained in Distinguished Names and
3130 on X.509 attribute certificates, respectively.
3136 - Added basic Mode Config functionality
3138 - Added Mathieu Lafon's patch which upgrades the status of
3139 the NAT-Traversal implementation to RFC 3947.
3141 - The _startklips script now also loads the xfrm4_tunnel
3144 - Added Ulrich Weber's netlink replay window size and
3145 maximum udp size patches.
3147 - UML testing now uses the Linux 2.6.10 UML kernel by default.
3153 - Eric Marchionni and Patrik Rayo, both recent graduates from
3154 the Zuercher Hochschule Winterthur in Switzerland, created a
3155 User-Mode-Linux test setup for strongSwan. For more details
3156 please read the INSTALL and README documents in the testing
3159 - Full support of group attributes based on X.509 attribute
3160 certificates. Attribute certificates can be generated
3161 using the openac facility. For more details see
3165 The group attributes can be used in connection definitions
3166 in order to give IPsec access to specific user groups.
3167 This is done with the new parameter left|rightgroups as in
3169 rightgroups="Research, Sales"
3171 giving access to users possessing the group attributes
3172 Research or Sales, only.
3174 - In Quick Mode clients with subnet mask /32 are now
3175 coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should
3176 fix rekeying problems with the SafeNet/SoftRemote and NCP
3177 Secure Entry Clients.
3179 - Changed the defaults of the ikelifetime and keylife parameters
3180 to 3h and 1h, respectively. The maximum allowable values are
3181 now both set to 24 h.
3183 - Suppressed notification wars between two IPsec peers that
3184 could e.g. be triggered by incorrect ISAKMP encryption.
3186 - Public RSA keys can now have identical IDs if either the
3187 issuing CA or the serial number is different. The serial
3188 number of a certificate is now shown by the command
3190 ipsec auto --listpubkeys
3196 - Added Tuomo Soini's sourceip feature which allows a strongSwan
3197 roadwarrior to use a fixed Virtual IP (see README section 2.6)
3198 and reduces the well-known four tunnel case on VPN gateways to
3199 a single tunnel definition (see README section 2.4).
3201 - Fixed a bug occurring with NAT-Traversal enabled when the responder
3202 suddenly turns initiator and the initiator cannot find a matching
3203 connection because of the floated IKE port 4500.
3205 - Removed misleading ipsec verify command from barf.
3207 - Running under the native IP stack, ipsec --version now shows
3208 the Linux kernel version (courtesy to the Openswan project).
3214 - Introduced the ipsec auto --listalgs monitoring command which lists
3215 all currently registered IKE and ESP algorithms.
3217 - Fixed a bug in the ESP algorithm selection occurring when the strict flag
3218 is set and the first proposed transform does not match.
3220 - Fixed another deadlock in the use of the lock_certs_and_keys() mutex,
3221 occurring when a smartcard is present.
3223 - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event.
3225 - Fixed the printing of the notification names (null)
3227 - Applied another of Herbert Xu's Netlink patches.
3233 - Support of Dead Peer Detection. The connection parameter
3235 dpdaction=clear|hold
3237 activates DPD for the given connection.
3239 - The default Opportunistic Encryption (OE) policy groups are not
3240 automatically included anymore. Those wishing to activate OE can include
3241 the policy group with the following statement in ipsec.conf:
3243 include /etc/ipsec.d/examples/oe.conf
3245 The default for [right|left]rsasigkey is now set to %cert.
3247 - strongSwan now has a Vendor ID of its own which can be activated
3248 using the compile option VENDORID
3250 - Applied Herbert Xu's patch which sets the compression algorithm correctly.
3252 - Applied Herbert Xu's patch fixing an ESPINUDP problem
3254 - Applied Herbert Xu's patch setting source/destination port numbers.
3256 - Reapplied one of Herbert Xu's NAT-Traversal patches which got
3257 lost during the migration from SuperFreeS/WAN.
3259 - Fixed a deadlock in the use of the lock_certs_and_keys() mutex.
3261 - Fixed the unsharing of alg parameters when instantiating group
3268 - Thomas Walpuski made me aware of a potential DoS attack via
3269 a PKCS#7-wrapped certificate bundle which could overwrite valid CA
3270 certificates in Pluto's authority certificate store. This vulnerability
3271 was fixed by establishing trust in CA candidate certificates up to a
3272 trusted root CA prior to insertion into Pluto's chained list.
3274 - replaced the --assign option by the -v option in the auto awk script
3275 in order to make it run with mawk under debian/woody.
3281 - Split of the status information between ipsec auto --status (concise)
3282 and ipsec auto --statusall (verbose). Both commands can be used with
3283 an optional connection selector:
3285 ipsec auto --status[all] <connection_name>
3287 - Added the description of X.509 related features to the ipsec_auto(8)
3290 - Hardened the ASN.1 parser in debug mode, especially the printing
3291 of malformed distinguished names.
3293 - The size of an RSA public key received in a certificate is now restricted to
3295 512 bits <= modulus length <= 8192 bits.
3297 - Fixed the debug mode enumeration.
3303 - Fixed another PKCS#7 vulnerability which could lead to an
3304 endless loop while following the X.509 trust chain.
3310 - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski
3311 that accepted end certificates having identical issuer and subject
3312 distinguished names in a multi-tier X.509 trust chain.
3318 - Removed all remaining references to ipsec_netlink.h in KLIPS.
3324 - The new "ca" section allows to define the following parameters:
3327 cacert=koolCA.pem # cacert of kool CA
3328 ocspuri=http://ocsp.kool.net:8001 # ocsp server
3329 ldapserver=ldap.kool.net # default ldap server
3330 crluri=http://www.kool.net/kool.crl # crl distribution point
3331 crluri2="ldap:///O=Kool, C= .." # crl distribution point #2
3332 auto=add # add, ignore
3334 The ca definitions can be monitored via the command
3336 ipsec auto --listcainfos
3338 - Fixed cosmetic corruption of /proc filesystem by integrating
3339 D. Hugh Redelmeier's freeswan-2.06 kernel fixes.
3345 - Added support for the 818043 NAT-Traversal update of Microsoft's
3346 Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode.
3348 - A symbolic link to libcrypto is now added in the kernel sources
3349 during kernel compilation
3351 - Fixed a couple of 64 bit issues (mostly casts to int).
3352 Thanks to Ken Bantoft who checked my sources on a 64 bit platform.
3354 - Replaced s[n]printf() statements in the kernel by ipsec_snprintf().
3355 Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro
3356 of the FreeS/WAN team who solved this problem with the 2.4.25 kernel.
3362 - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName
3363 certificate extension which contains no generalName item) can cause
3364 a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has
3365 been hardened to make it more robust against malformed ASN.1 objects.
3367 - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native
3368 Linux 2.6 IPsec stack.
3374 - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12