4 - Fixed a denial-of-service vulnerability in the gmp plugin that was caused by
5 an integer overflow when processing RSASSA-PSS signatures with very large
7 This vulnerability has been registered as CVE-2021-41990.
9 - Fixed a denial-of-service vulnerabililty in the in-memory certificate cache
10 if certificates are replaced and a very large random value caused an integer
12 This vulnerability has been registered as CVE-2021-41991.
14 - Fixed a related flaw that caused the daemon to accept an infinite number of
15 versions of a valid certificate by modifying the parameters in the
16 signatureAlgorithm field of the outer X.509 Certificate structure.
18 - AUTH_LIFETIME notifies are now only sent by a responder if it can't
19 reauthenticate the IKE_SA itself due to asymmetric authentication (i.e. EAP)
20 or the use of virtual IPs.
22 - Serial number generation in several pki sub-commands has been fixed so they
23 don't start with an unintended zero byte.
25 - Initialize libtpmtss in all programs and library that use it.
27 - Migrated testing scripts to Python 3.
33 - Added AES_ECB, SHA-3 and SHAKE-256 support to wolfssl plugin.
35 - Added AES_CCM and SHA-3 signature support to openssl plugin.
37 - The x509 and openssl plugins now consider the authorityKeyIdentifier, if
38 available, before verifying signatures, which avoids unnecessary signature
39 verifications after a CA key rollover if both certificates are loaded.
41 - The pkcs11 plugin better handles optional attributes like CKA_TRUSTED, which
42 previously depended on a version check.
44 - charon-nm now supports using SANs as client identities, not only full DNs.
46 - charon-tkm now handles IKE encryption.
48 - A MOBIKE update is sent again if a a change in the NAT mappings is detected
49 but the endpoints stay the same.
51 - Converted most of the test case scenarios to the vici interface
57 - Together with a Linux 5.8 kernel supporting the IMA measurement of the GRUB
58 bootloader and the Linux kernel, the strongSwan Attestation IMC allows to do
59 remote attestation of the complete boot phase. A recent TPM 2.0 device with a
60 SHA-256 PCR bank is required, so that both BIOS and IMA file measurements are
61 based on SHA-256 hashes.
63 - Our own TLS library (libtls) that we use for TLS-based EAP methods and PT-TLS
64 gained experimental support for TLS 1.3. Thanks to Méline Sieber (client) and
65 Pascal Knecht (client and server) for their work on this.
66 Because the use of TLS 1.3 with these EAP methods is not yet standardized (two
67 Internet-Drafts are being worked on), the default maximum version is currently
68 set to TLS 1.2, which is now also the default minimum version. However the TNC
69 test scenarios using PT-TLS transport already use TLS 1.3.
71 - Other improvements for libtls also affect older TLS versions. For instance, we
72 added support for ECDH with Curve25519/448 (DH groups may also be configured
73 now), for EdDSA keys and certificates and for RSA-PSS signatures. Support for
74 old and weak cipher suites has been removed (e.g. with 3DES and MD5) as well
75 as signature schemes with SHA-1.
77 - The listener_t::ike_update event is now also called for MOBIKE updates. Its
78 signature has changed so we only have to call it once if both addresses/ports
79 have changed (e.g. for an address family switch). The event is now also
82 - The farp plugin has been ported to macOS and FreeBSD. Thanks to Dan James for
85 - To fix DNS server installation with systemd-resolved, charon-nm now creates a
86 dummy TUN device again (was removed with 5.5.1).
88 - The botan plugin can use rng_t implementations provided by other plugins when
89 generating keys etc. if the Botan library supports it.
91 - charon-tkm now supports multiple CAs and is configured via vici/swanctl.
93 - Simple glob patterns (e.g. include conf.d/*.conf) now also work on Windows.
94 Handling of forward slashes in paths on Windows has also been improved.
96 - The abbreviations for the 'surname' and 'serial number' RDNs in ASN.1 DNs have
97 been changed to align with RFC 4519: The abbreviation for 'surname' is now
98 "SN" (was "S" before), which was previously used for 'serial number' that can
99 now be specified as "serialNumber" only.
101 - An issue with Windows clients requesting previous IPv6 but not IPv4 virtual
102 IP addresses has been fixed.
104 - ike_sa_manager_t: Checking out IKE_SAs by config is now atomic (e.g. when
105 acquires for different children of the same connection arrive concurrently).
106 The checkout_new() method has been renamed to create_new(). A new
107 checkout_new() method allows registering a new IKE_SA with the manager before
108 checking it in, so jobs can be queued without losing them as they can block
109 on checking out the new SA.
115 - Remote attestation via TNC supports the SHA-256 based TPM 2.0 BIOS/EFI
116 measurements introduced with the Linux 5.4 kernel.
118 - Nonces in OCSP responses are not enforced anymore and only validated if a
119 nonce is actually contained.
121 - Fixed an issue when only some fragments of a retransmitted IKEv2 message were
122 received, which prevented processing a following fragmented message.
124 - All queued vici messages are now sent to subscribed clients during shutdown,
125 which includes ike/child-updown events triggered when all SAs are deleted.
127 - CHILD_SA IP addresses are updated before installation to allow MOBIKE updates
128 while retransmitting a CREATE_CHILD_SA request.
130 - When looking for a route to the peer, the kernel-netlink plugin ignores the
131 current source address if it's deprecated.
133 - The file and syslog loggers support logging the log level of each message
134 after the subsystem (e.g. [IKE2]).
136 - charon-nm is now properly terminated during system shutdown.
138 - Improved support for EdDSA keys in vici/swanctl, in particular, encrypted
139 keys are now supported.
141 - A new global strongswan.conf option allows sending the Cisco FlexVPN vendor ID
142 to prevent Cisco devices from narrowing a 0.0.0.0/0 traffic selector.
144 - The openssl plugin accepts CRLs issued by non-CA certificates if they contain
145 the cRLSign keyUsage flag (the x509 plugin already does this since 4.5.1).
147 - Attributes in PKCS#7 containers, as used in SCEP, are now properly
148 DER-encoded, i.e. sorted.
150 - The load-tester plugin now supports virtual IPv6 addresses and IPv6 source
157 - We prefer AEAD algorithms for ESP and therefore put AES-GCM in a default AEAD
158 proposal in front of the previous default proposal.
160 - The NM backend now clears cached credentials when disconnecting, has DPD and
161 and close action set to restart, and supports custom remote TS via 'remote-ts'
162 option (no GUI support).
164 - The pkcs11 plugin falls back to software hashing for PKCS#1v1.5 RSA signatures
165 if mechanisms with hashing (e.g. CKM_SHA256_RSA_PKCS) are not supported.
167 - The owner/group of log files is now set so the daemon can reopen them if the
168 config is reloaded and it doesn't run as root.
170 - The wolfssl plugin (with wolfSSL 4.4.0+) supports x448 DH and Ed448 keys.
172 - The vici plugin stores all CA certificates in one location, which avoids
173 issues with unloading authority sections or clearing all credentials.
175 - When unloading a vici connection with start_action=start, any related IKE_SAs
176 without children are now terminated (including those in CONNECTING state).
178 - The hashtable implementation has been changed so it maintains insertion order.
179 This was mainly done so the vici plugin can store its connections in a
180 hashtable, which makes managing high numbers of connections faster.
182 - The default maximum size for vici messages (512 KiB) can now be changed via
183 VICI_MESSAGE_SIZE_MAX compile option.
185 - The charon.check_current_path option allows forcing a DPD exchange to check if
186 the current path still works whenever interface/address-changes are detected.
188 - It's possible to use clocks other than CLOCK_MONOTONIC (e.g. CLOCK_BOOTTIME)
189 via TIME_CLOCK_ID compile option if clock_gettime() is available and
190 pthread_condattr_setclock() supports that clock.
192 - Test cases and functions can now be filtered when running the unit tests.
198 - In IKEv1 Quick Mode make sure that a proposal exists before determining
199 lifetimes (fixes crash due to null pointer exception).
201 - OpenSSL currently doesn't support squeezing bytes out of a SHAKE128/256
202 XOF (eXtended Output Function) multiple times. Unfortunately,
203 EVP_DigestFinalXOF() completely resets the context and later calls not
204 simply fail, they cause a null-pointer dereference in libcrypto. This
205 fixes the crash at the cost of repeating initializing the whole state
206 and allocating too much data for subsequent calls.
212 - Updates for the NM backend (and plugin), among others: EAP-TLS authentication,
213 configurable local and remote IKE identities, custom server port, redirection
214 and reauthentication support.
216 - Previously used reqids are now reallocated to workaround an issue on FreeBSD
217 where the daemon can't use reqids > 16383.
219 - On Linux, throw type routes are installed for passthrough policies. They act
220 as fallbacks on routes in other tables and require less information, so they
221 can be installed earlier and are not affected by updates.
223 - For IKEv1, the lifetimes of the selected transform are returned to the
224 initiator, which is an issue with peers that propose different lifetimes in
225 different transforms. We also return the correct transform and proposal IDs.
227 - IKE_SAs are not re-established anymore if a deletion has been queued.
229 - Added support for Ed448 keys and certificates via openssl plugin and pki tool.
230 The openssl plugin also supports SHA-3 and SHAKE128/256.
232 - The use of algorithm IDs from the private use ranges can now be enabled
233 globally, to use them even if no strongSwan vendor ID was exchanged.
239 - Identity-based CA constraints are supported via vici/swanctl.conf. They
240 enforce that the remote's certificate chain contains a CA certificate with a
241 specific identity. While similar to the existing CA constraints, they don't
242 require that the CA certificate is locally installed such as intermediate CA
243 certificates received from peers. Compared to wildcard identity matching (e.g.
244 "..., OU=Research, CN=*") this requires less trust in the intermediate CAs (to
245 only issue certificates with legitimate subject DNs) as long as path length
246 basic constraints prevent them from issuing further intermediate CAs.
248 - Intermediate CA certificates may now be sent in hash-and-URL encoding by
249 configuring a base URL for the parent CA.
251 - Implemented NIST SP-800-90A Deterministic Random Bit Generator (DRBG)
252 based on AES-CTR and SHA2-HMAC modes. Currently used by gmp and ntru plugins.
254 - Random nonces sent in an OCSP requests are now expected in the corresponding
257 - The kernel-netlink plugin ignores deprecated IPv6 addresses for MOBIKE.
258 Whether temporary or permanent IPv6 addresses are included depends on the
259 charon.prefer_temporary_addrs setting.
261 - Extended Sequence Numbers (ESN) are configured via PF_KEY if supported by the
264 - Unique section names are used for CHILD_SAs in vici child-updown events and
265 more information (e.g. statistics) are included for individually deleted
266 CHILD_SAs (in particular for IKEv1).
268 - So fallbacks to other plugins work properly, creating HMACs via openssl plugin
269 now fails instantly if the underlying hash algorithm isn't supported (e.g.
272 - Exponents of RSA keys read from TPM 2.0 via SAPI are now correctly converted.
274 - Routing table IDs > 255 are supported for custom routes on Linux.
276 - The D-Bus config file for charon-nm is now installed in
277 $(datadir)/dbus-1/system.d instead of $(sysconfdir)/dbus-1/system.d.
279 - INVALID_MAJOR_VERSION notifies are now correctly sent in messages of the same
280 exchange type and using the same message ID as the request.
282 - IKEv2 SAs are immediately destroyed when sending or receiving INVALID_SYNTAX
283 notifies in authenticated messages.
289 - RDNs in Distinguished Names can now optionally be matched less strict. The
290 global option charon.rdn_matching takes two alternative values that cause the
291 matching algorithm to either ignore the order of matched RDNs or additionally
292 accept DNs that contain more RDNs than configured (unmatched RDNs are treated
293 like wildcard matches).
295 - The updown plugin now passes the same interface to the script that is also
296 used for the automatically installed routes, i.e. the interface over which the
297 peer is reached instead of the interface on which the local address is found.
299 - TPM 2.0 contexts are now protected by a mutex to prevent issues if multiple
300 IKE_SAs use the same private key concurrently.
306 - The systemd service units have been renamed. The modern unit, which was called
307 strongswan-swanctl, is now called strongswan (the previous name is configured
308 as alias). The legacy unit is now called strongswan-starter.
310 - Support for XFRM interfaces (available since Linux 4.19) has been added.
311 Configuration is possible via swanctl.conf. Interfaces may be created
312 dynamically via updown/vici scripts, or statically before or after
313 establishing the SAs. Routes must be added manually as needed (the daemon will
314 not install any routes for outbound policies with an interface ID).
316 - Initiation of childless IKE_SAs is supported (RFC 6023). If enabled and
317 supported by the responder, no CHILD_SA is established during IKE_AUTH. This
318 allows using a separate DH exchange even for the first CHILD_SA, which is
319 otherwise created with keys derived from the IKE_SA's key material.
321 - The NetworkManager backend and plugin support IPv6.
323 - The new wolfssl plugin is a wrapper around the wolfSSL crypto library. Thanks
324 to Sean Parkinson of wolfSSL Inc. for the initial patch.
326 - IKE SPIs may optionally be labeled via the charon.spi_mask|label options. This
327 feature was extracted from charon-tkm, however, now applies the mask/label in
330 - The openssl plugin supports ChaCha20-Poly1305 when built with OpenSSL 1.1.0.
332 - The PB-TNC finite state machine according to section 3.2 of RFC 5793 was not
333 correctly implemented when sending either a CRETRY or SRETRY batch. These
334 batches can only be sent in the "Decided" state and a CRETRY batch can
335 immediately carry all messages usually transported by a CDATA batch. It is
336 currently not possible to send a SRETRY batch since full-duplex mode for
337 PT-TLS transport is not supported.
339 - Instead of marking virtual IPv6 addresses as deprecated, the kernel-netlink
340 plugin uses address labels to avoid their use for non-VPN traffic.
342 - The agent plugin creates sockets to the ssh/gpg-agent dynamically and does not
343 keep them open, which otherwise can prevent the agent from getting terminated.
345 - To avoid broadcast loops the forecast plugin now only reinjects packets that
346 are marked or received from the configured interface.
348 - UTF-8 encoded passwords are supported via EAP-MSCHAPv2, which internally uses
349 an UTF-16LE encoding to calculate the NT hash.
351 - Adds the build-certs script to generate the keys and certificates used for
352 regression tests dynamically. They are built with the pki version installed
353 in the KVM root image so it's not necessary to have an up-to-date version with
354 all required plugins installed on the host system.
360 - Private key implementations may optionally provide a list of supported
361 signature schemes, which is used by the tpm plugin because for each key on a
362 TPM 2.0 the hash algorithm and for RSA also the padding scheme is predefined.
364 - For RSA with PSS padding, the TPM 2.0 specification mandates the maximum salt
365 length (as defined by the length of the key and hash). However, if the TPM is
366 FIPS-168-4 compliant, the salt length equals the hash length. This is assumed
367 for FIPS-140-2 compliant TPMs, but if that's not the case, it might be
368 necessary to manually enable charon.plugins.tpm.fips_186_4 if the TPM doesn't
369 use the maximum salt length.
371 - swanctl now accesses directories for credentials relative to swanctl.conf, in
372 particular, when it's loaded from a custom location via --file argument. The
373 base directory that's used if --file is not given is configurable at runtime
374 via SWANCTL_DIR environment variable.
376 - With RADIUS Accounting enabled, the eap-radius plugin adds the session ID to
377 Access-Request messages, simplifying associating database entries for IP
378 leases and accounting with sessions.
380 - IPs assigned by RADIUS servers are included in Accounting-Stop even if clients
381 don't claim them, allowing releasing them early on connection errors.
383 - Selectors installed on transport mode SAs by the kernel-netlink plugin are
384 updated on IP address changes (e.g. via MOBIKE).
386 - Added support for RSA signatures with SHA-256 and SHA-512 to the agent plugin.
387 For older versions of ssh/gpg-agent that only support SHA-1, IKEv2 signature
388 authentication has to be disabled via charon.signature_authentication.
390 - The sshkey and agent plugins support Ed25519/Ed448 SSH keys and signatures.
392 - The openssl plugin supports X25519/X448 Diffie-Hellman and Ed25519/Ed448 keys
393 and signatures when built against OpenSSL 1.1.1.
395 - Ed25519, ChaCha20/Poly1305, SHA-3 and AES-CCM were added to the botan plugin.
397 - The mysql plugin now properly handles database connections with transactions
400 - IP addresses in HA pools are now distributed evenly among all segments.
402 - On newer FreeBSD kernels, the kernel-pfkey plugin reads the reqid directly
403 from SADB_ACQUIRE messages, i.e. not requiring previous policy installation by
404 the plugin, e.g. for compatibility with if_ipsec(4) VTIs.
410 - Fixes a vulnerability in the gmp plugin triggered by crafted certificates with
411 RSA keys with very small moduli. When verifying signatures with such keys,
412 the code patched with the fix for CVE-2018-16151/2 caused an integer underflow
413 and subsequent heap buffer overflow that results in a crash of the daemon.
414 The vulnerability has been registered as CVE-2018-17540.
420 - Fixes a potential authorization bypass vulnerability in the gmp plugin that
421 was caused by a too lenient verification of PKCS#1 v1.5 signatures. Several
422 flaws could be exploited by a Bleichenbacher-style attack to forge signatures
423 for low-exponent keys (i.e. with e=3). CVE-2018-16151 has been assigned to
424 the problem of accepting random bytes after the OID of the hash function in
425 such signatures, and CVE-2018-16152 has been assigned to the issue of not
426 verifying that the parameters in the ASN.1 algorithmIdentifier structure is
427 empty. Other flaws that don't lead to a vulnerability directly (e.g. not
428 checking for at least 8 bytes of padding) have no separate CVE assigned.
430 - Dots are not allowed anymore in section names in swanctl.conf and
431 strongswan.conf. This mainly affects the configuration of file loggers. If the
432 path for such a log file contains dots it now has to be configured in the new
433 `path` setting within the arbitrarily renamed subsection in the `filelog`
436 - Sections in swanctl.conf and strongswan.conf may now reference other sections.
437 All settings and subsections from such a section are inherited. This allows
438 to simplify configs as redundant information has only to be specified once
439 and may then be included in other sections (refer to the example in the man
440 page for strongswan.conf).
442 - The originally selected IKE config (based on the IPs and IKE version) can now
443 change if no matching algorithm proposal is found. This way the order
444 of the configs doesn't matter that much anymore and it's easily possible to
445 specify separate configs for clients that require weak algorithms (instead
446 of having to also add them in other configs that might be selected).
448 - Support for Postquantum Preshared Keys for IKEv2 (draft-ietf-ipsecme-qr-ikev2)
451 - The new botan plugin is a wrapper around the Botan C++ crypto library. It
452 requires a fairly recent build from Botan's master branch (or the upcoming
453 2.8.0 release). Thanks to René Korthaus and his team from Rohde & Schwarz
454 Cybersecurity for the initial patch.
456 - The pki tool accepts a xmppAddr otherName as a subjectAlternativeName using
457 the syntax --san xmppaddr:<jid>.
459 - Implementation of RFC 8412 "Software Inventory Message and Attributes (SWIMA)
460 for PA-TNC". SWIMA subscription option sets CLOSE_WRITE trigger on apt
461 history.log file resulting in a ClientRetry PB-TNC batch to initialize
462 a new measurement cycle.
464 - Added support for fuzzing the PA-TNC (RFC 5792) and PB-TNC (RFC 5793) NEA
465 protocols on Google's OSS-Fuzz infrastructure.
467 - Support for version 2 of Intel's TPM2-TSS TGC Software Stack. The presence of
468 the in-kernel /dev/tpmrm0 resource manager is automatically detected.
470 - Marks the in- and/or outbound SA should apply to packets after processing may
471 be configured in swanctl.conf on Linux. For outbound SAs this requires at
472 least a 4.14 kernel. Setting a mask and configuring a mark/mask for inbound
473 SAs will be added with the upcoming 4.19 kernel.
475 - New options in swanctl.conf allow configuring how/whether DF, ECN and DS
476 fields in the IP headers are copied during IPsec processing. Controlling this
477 is currently only possible on Linux.
479 - To avoid conflicts, the dhcp plugin now only uses the DHCP server port if
480 explicitly configured.
486 - Fixed a DoS vulnerability in the IKEv2 key derivation if the openssl plugin is
487 used in FIPS mode and HMAC-MD5 is negotiated as PRF.
488 This vulnerability has been registered as CVE-2018-10811.
490 - Fixed a vulnerability in the stroke plugin, which did not check the received
491 length before reading a message from the socket. Unless a group is configured,
492 root privileges are required to access that socket, so in the default
493 configuration this shouldn't be an issue.
494 This vulnerability has been registered as CVE-2018-5388.
496 ⁻ CRLs that are not yet valid are now ignored to avoid problems in scenarios
497 where expired certificates are removed from CRLs and the clock on the host
498 doing the revocation check is trailing behind that of the host issuing CRLs.
500 - The issuer of fetched CRLs is now compared to the issuer of the checked
503 - CRL validation results other than revocation (e.g. a skipped check because
504 the CRL couldn't be fetched) are now stored also for intermediate CA
505 certificates and not only for end-entity certificates, so a strict CRL policy
506 can be enforced in such cases.
508 - In compliance with RFC 4945, section 5.1.3.2, certificates used for IKE must
509 now either not contain a keyUsage extension (like the ones generated by pki)
510 or have at least one of the digitalSignature or nonRepudiation bits set.
512 - New options for vici/swanctl allow forcing the local termination of an IKE_SA.
513 This might be useful in situations where it's known the other end is not
514 reachable anymore, or that it already removed the IKE_SA, so retransmitting a
515 DELETE and waiting for a response would be pointless. Waiting only a certain
516 amount of time for a response before destroying the IKE_SA is also possible
517 by additionally specifying a timeout.
519 - When removing routes, the kernel-netlink plugin now checks if it tracks other
520 routes for the same destination and replaces the installed route instead of
521 just removing it. Same during installation, where existing routes previously
522 weren't replaced. This should allow using traps with virtual IPs on Linux.
524 - The dhcp plugin only sends the client identifier option if identity_lease is
525 enabled. It can also send identities of up to 255 bytes length, instead of
526 the previous 64 bytes. If a server address is configured, DHCP requests are
527 now sent from port 67 instead of 68 to avoid ICMP port unreachables.
529 - Roam events are now completely ignored for IKEv1 SAs.
531 - ChaCha20/Poly1305 is now correctly proposed without key length. For
532 compatibility with older releases the chacha20poly1305compat keyword may be
533 included in proposals to also propose the algorithm with a key length.
535 - Configuration of hardware offload of IPsec SAs is now more flexible and allows
536 a new mode, which automatically uses it if the kernel and device support it.
538 - SHA-2 based PRFs are supported in PKCS#8 files as generated by OpenSSL 1.1.
540 - The pki --verify tool may load CA certificates and CRLs from directories.
542 - Fixed an issue with DNS servers passed to NetworkManager in charon-nm.
548 - Fixed a DoS vulnerability in the parser for PKCS#1 RSASSA-PSS signatures that
549 was caused by insufficient input validation. One of the configurable
550 parameters in algorithm identifier structures for RSASSA-PSS signatures is the
551 mask generation function (MGF). Only MGF1 is currently specified for this
552 purpose. However, this in turn takes itself a parameter that specifies the
553 underlying hash function. strongSwan's parser did not correctly handle the
554 case of this parameter being absent, causing an undefined data read.
555 This vulnerability has been registered as CVE-2018-6459.
557 - The previously negotiated DH group is reused when rekeying an SA, instead of
558 using the first group in the configured proposals, which avoids an additional
559 exchange if the peer selected a different group via INVALID_KE_PAYLOAD when
560 the SA was created initially.
561 The selected DH group is also moved to the front of all sent proposals that
562 contain it and all proposals that don't are moved to the back in order to
563 convey the preference for this group to the peer.
565 - Handling of MOBIKE task queuing has been improved. In particular, the response
566 to an address update is not ignored anymore if only an address list update or
569 - The fallback drop policies installed to avoid traffic leaks when replacing
570 addresses in installed policies are now replaced by temporary drop policies,
571 which also prevent acquires because we currently delete and reinstall IPsec
572 SAs to update their addresses.
574 - Access X.509 certificates held in non-volatile storage of a TPM 2.0
575 referenced via the NV index.
577 - Adding the --keyid parameter to pki --print allows to print private keys
578 or certificates stored in a smartcard or a TPM 2.0.
580 - Fixed proposal selection if a peer incorrectly sends DH groups in the ESP
581 proposals during IKE_AUTH and also if a DH group is configured in the local
582 ESP proposal and charon.prefer_configured_proposals is disabled.
584 - MSKs received via RADIUS are now padded to 64 bytes to avoid compatibility
585 issues with EAP-MSCHAPv2 and PRFs that have a block size < 64 bytes (e.g.
588 - The tpm_extendpcr command line tool extends a digest into a TPM PCR.
590 - Ported the NetworkManager backend from the deprecated libnm-glib to libnm.
592 - The save-keys debugging/development plugin saves IKE and/or ESP keys to files
593 compatible with Wireshark.
599 - In compliance with RFCs 8221 and 8247 several algorithms were removed from the
600 default ESP/AH and IKEv2 proposals, respectively (3DES, Blowfish and MD5 from
601 ESP/AH, MD5 and MODP-1024 from IKEv2). These algorithms may still be used in
604 - Added support for RSASSA-PSS signatures. For backwards compatibility they are
605 not used automatically by default, enable charon.rsa_pss to change that. To
606 explicitly use or require such signatures with IKEv2 signature authentication
607 (RFC 7427), regardless of whether that option is enabled, use ike:rsa/pss...
608 authentication constraints.
610 - The pki tool can optionally sign certificates/CRLs with RSASSA-PSS via the
611 `--rsa-padding pss` option.
613 - The sec-updater tool checks for security updates in dpkg-based repositories
614 (e.g. Debian/Ubuntu) and sets the security flags in the IMV policy database
615 accordingly. Additionally for each new package version a SWID tag for the
616 given OS and HW architecture is created and stored in the database.
617 Using the sec-updater.sh script template the lookup can be automated
618 (e.g. via an hourly cron job).
620 - The introduction of file versions in the IMV database scheme broke file
621 reference hash measurements. This has been fixed by creating generic product
622 versions having an empty package name.
624 - A new timeout option for the systime-fix plugin stops periodic system time
625 checks after a while and enforces a certificate verification, closing or
626 reauthenticating all SAs with invalid certificates.
628 - The IKE event counters, previously only available via ipsec listcounters, may
629 now be queried/reset via vici and the new swanctl --counters command. They are
630 provided by the new optional counters plugin.
632 - Class attributes received in RADIUS Access-Accept messages may optionally be
633 added to RADIUS accounting messages.
635 - Inbound marks may optionally be installed on the SA again (was removed with
636 5.5.2) by enabling the mark_in_sa option in swanctl.conf.
642 - Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
643 input validation when verifying RSA signatures, which requires decryption
644 with the operation m^e mod n, where m is the signature, and e and n are the
645 exponent and modulus of the public key. The value m is an integer between
646 0 and n-1, however, the gmp plugin did not verify this. So if m equals n the
647 calculation results in 0, in which case mpz_export() returns NULL. This
648 result wasn't handled properly causing a null-pointer dereference.
649 This vulnerability has been registered as CVE-2017-11185.
651 - New SWIMA IMC/IMV pair implements the "draft-ietf-sacm-nea-swima-patnc"
652 Internet Draft and has been demonstrated at the IETF 99 Prague Hackathon.
654 - The IMV database template has been adapted to achieve full compliance
655 with the ISO 19770-2:2015 SWID tag standard.
657 - The sw-collector tool extracts software events from apt history logs
658 and stores them in an SQLite database to be used by the SWIMA IMC.
659 The tool can also generate SWID tags both for installed and removed
662 - The pt-tls-client can attach and use TPM 2.0 protected private keys
663 via the --keyid parameter.
665 - libtpmtss supports Intel's TSS2 Architecture Broker and Resource
666 Manager interface (tcti-tabrmd).
668 - The new eap-aka-3gpp plugin implements the 3GPP MILENAGE algorithms
669 in software. K (optionally concatenated with OPc) may be configured as
672 - CHILD_SA rekeying was fixed in charon-tkm and was slightly changed: The
673 switch to the new outbound IPsec SA now happens via SPI on the outbound
674 policy on Linux, and in case of lost rekey collisions no outbound SA/policy
675 is temporarily installed for the redundant CHILD_SA.
677 - The new %unique-dir value for mark* settings allocates separate unique marks
678 for each CHILD_SA direction (in/out).
684 - Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
685 input validation when verifying RSA signatures. More specifically,
686 mpz_powm_sec() has two requirements regarding the passed exponent and modulus
687 that the plugin did not enforce, if these are not met the calculation will
688 result in a floating point exception that crashes the whole process.
689 This vulnerability has been registered as CVE-2017-9022.
691 - Fixed a DoS vulnerability in the x509 plugin that was caused because the ASN.1
692 parser didn't handle ASN.1 CHOICE types properly, which could result in an
693 infinite loop when parsing X.509 extensions that use such types.
694 This vulnerability has been registered as CVE-2017-9023.
696 - The behavior during IKEv2 CHILD_SA rekeying has been changed in order to avoid
697 traffic loss. The responder now only installs the new inbound SA and delays
698 installing the outbound SA until it receives the DELETE for the replaced
699 CHILD_SA. Similarly, the inbound SA of the replaced CHILD_SA is not removed
700 for a configurable amount of seconds (charon.delete_rekeyed_delay) after the
701 DELETE has been processed to reduce the chance of dropping delayed packets.
703 - The code base has been ported to Apple's ARM64 iOS platform, whose calling
704 conventions for variadic and regular functions are different. This means
705 assigning non-variadic functions to variadic function pointers does not work.
706 To avoid this issue the enumerator_t interface has been changed and the
707 signatures of the callback functions for enumerator_create_filter(), and the
708 invoke_function() and find_first() methods on linked_list_t have been changed.
709 The return type of find_first() also changed from status_t to bool.
711 - Added support for fuzzing the certificate parser provided by the default
712 plugins (x509, pem, gmp etc.) on Google's OSS-Fuzz infrastructure. Several
713 issues found while fuzzing these plugins were fixed.
715 - Two new options have been added to charon's retransmission settings:
716 retransmit_limit and retransmit_jitter. The former adds an upper limit to the
717 calculated retransmission timeout, the latter randomly reduces it.
719 - A bug in swanctl's --load-creds command was fixed that caused unencrypted
720 private keys to get unloaded if the command was called multiple times. The
721 load-key VICI command now returns the key ID of the loaded key on success.
723 - The credential manager now enumerates local credential sets before global
724 ones. This means certificates supplied by the peer will now be preferred over
725 certificates with the same identity that may be locally stored (e.g. in the
728 - Added support for hardware offload of IPsec SAs as introduced by Linux 4.11
729 for hardware that supports this.
731 - When building the libraries monolithically and statically the plugin
732 constructors are now hard-coded in each library so the plugin code is not
733 removed by the linker because it thinks none of their symbols are ever
736 - The pki tool loads the curve25519 plugin by default.
742 - Support of Diffie-Hellman group 31 using Curve25519 for IKE as defined
745 - Support of Ed25519 digital signature algorithm for IKEv2 as defined by
746 draft-ietf-ipsecme-eddsa. Ed25519-based public key pairs, X.509 certificates
747 and CRLs can be generated and printed by the pki tool.
749 - The new "tpm" libtpmtss plugin allows to use persistent private RSA and ECDSA
750 keys bound to a TPM 2.0 for both IKE and TLS authentication. Using the
751 TPM 2.0 object handle as keyid parameter, the pki --pub tool can extract
752 the public key from the TPM thereby replacing the aikpub2 tool. In a similar
753 fashion pki --req can generate a PKCS#10 certificate request signed with
756 - The pki tool gained support for generating certificates with the RFC 3779
757 addrblock extension. The charon addrblock plugin now dynamically narrows
758 traffic selectors based on the certificate addrblocks instead of rejecting
759 non-matching selectors completely. This allows generic connections, where
760 the allowed selectors are defined by the used certificates only.
762 - In-place update of cached base and delta CRLs does not leave dozens
763 of stale copies in cache memory.
765 - Several new features for the VICI interface and the swanctl utility: Querying
766 specific pools, enumerating and unloading keys and shared secrets, loading
767 keys and certificates from PKCS#11 tokens, the ability to initiate, install
768 and uninstall connections and policies by their exact name (if multiple child
769 sections in different connections share the same name), a command to initiate
770 the rekeying of IKE and IPsec SAs, support for settings previously only
771 supported by the old config files (plain pubkeys, dscp, certificate policies,
772 IPv6 Transport Proxy Mode, NT Hash secrets, mediation extension).
774 Important: Due to issues with VICI bindings that map sub-sections to
775 dictionaries the CHILD_SA sections returned via list-sas now have a unique
776 name, the original name of a CHILD_SA is returned in the "name" key of its
783 - The newhope plugin implements the post-quantum NewHope key exchange algorithm
784 proposed in their 2015 paper by Erdem Alkim, Léo Ducas, Thomas Pöppelmann and
787 - The libstrongswan crypto factory now offers the registration of Extended
788 Output Functions (XOFs). Currently supported XOFs are SHAKE128 and SHAKE256
789 implemented by the sha3 plugin, ChaCHa20 implemented by the chapoly plugin
790 and the more traditional MGF1 Mask Generation Functions based on the SHA-1,
791 SHA-256 and SHA-512 hash algorithms implemented by the new mgf1 plugin.
793 - The pki tool, with help of the pkcs1 or openssl plugins, can parse private
794 keys in any of the supported formats without having to know the exact type.
795 So instead of having to specify rsa or ecdsa explicitly the keyword priv may
796 be used to indicate a private key of any type. Similarly, swanctl can load
797 any type of private key from the swanctl/private directory.
799 - The pki tool can handle RSASSA-PKCS1v1.5-with-SHA-3 signatures using the
800 sha3 and gmp plugins.
802 - The VICI flush-certs command flushes certificates from the volatile
803 certificate cache. Optionally the type of the certificates to be
804 flushed (e.g. type = x509_crl) can be specified.
806 - Setting cache_crls = yes in strongswan.conf the vici plugin saves regular,
807 base and delta CRLs to disk.
809 - IKE fragmentation is now enabled by default with the default fragment size
810 set to 1280 bytes for both IP address families.
812 - libtpmtss: In the TSS2 API the function TeardownSocketTcti() was replaced by
813 tss2_tcti_finalize().
819 - The new libtpmtss library offers support for both TPM 1.2 and TPM 2.0
820 Trusted Platform Modules. This allows the Attestation IMC/IMV pair to
821 do TPM 2.0 based attestation.
823 - The behavior during IKEv2 exchange collisions has been improved/fixed in
824 several corner cases and support for TEMPORARY_FAILURE and CHILD_SA_NOT_FOUND
825 notifies, as defined by RFC 7296, has been added.
827 - IPsec policy priorities can be set manually (e.g. for high-priority drop
828 policies) and outbound policies may be restricted to a network interface.
830 - The scheme for the automatically calculated default priorities has been
831 changed and now also considers port masks, which were added with 5.4.0.
833 - FWD policies are now installed in both directions in regards to the traffic
834 selectors. Because such "outbound" FWD policies could conflict with "inbound"
835 FWD policies of other SAs they are installed with a lower priority and don't
836 have a reqid set, which allows kernel plugins to distinguish between the two
837 and prefer those with a reqid.
839 - For outbound IPsec SAs no replay window is configured anymore.
841 - Enhanced the functionality of the swanctl --list-conns command by listing
842 IKE_SA and CHILD_SA reauthentication and rekeying settings, and EAP/XAuth
843 identities and EAP types.
845 - DNS servers installed by the resolve plugin are now refcounted, which should
846 fix its use with make-before-break reauthentication. Any output written to
847 stderr/stdout by resolvconf is now logged.
849 - The methods in the kernel interfaces have been changed to take structs instead
850 of long lists of arguments. Similarly the constructors for peer_cfg_t and
851 child_cfg_t now take structs.
857 - Support for IKEv2 redirection (RFC 5685) has been added. Plugins may
858 implement the redirect_provider_t interface to decide if and when to redirect
859 connecting clients. It is also possible to redirect established IKE_SAs based
860 on different selectors via VICI/swanctl. Unless disabled in strongswan.conf
861 the charon daemon will follow redirect requests received from servers.
863 - The ike: prefix enables the explicit configuration of signature scheme
864 constraints against IKEv2 authentication in rightauth, which allows the use
865 of different signature schemes for trustchain verification and authentication.
867 - The initiator of an IKEv2 make-before-break reauthentication now suspends
868 online certificate revocation checks (OCSP, CRLs) until the new IKE_SA and all
869 CHILD_SAs are established. This is required if the checks are done over the
870 CHILD_SA established with the new IKE_SA. This is not possible until the
871 initiator installs this SA and that only happens after the authentication is
872 completed successfully. So we suspend the checks during the reauthentication
873 and do them afterwards, if they fail the IKE_SA is closed. This change has no
874 effect on the behavior during the authentication of the initial IKE_SA.
876 - For the vici plugin a Vici:Session Perl CPAN module has been added to allow
877 Perl applications to control and/or monitor the IKE daemon using the VICI
878 interface, similar to the existing Python egg or Ruby gem.
880 - Traffic selectors with port ranges can now be configured in the Linux kernel:
881 e.g. remote_ts = 10.1.0.0/16[tcp/20-23] local_ts = dynamic[tcp/32768-65535].
882 The port range must map to a port mask, though since the kernel does not
883 support arbitrary ranges.
885 - The vici plugin allows the configuration of IPv4 and IPv6 address ranges
886 in local and remote traffic selectors. Since both the Linux kernel and
887 iptables cannot handle arbitrary ranges, address ranges are mapped to the next
888 larger CIDR subnet by the kernel-netlink and updown plugins, respectively.
890 - Implemented IKEv1 IPv4/IPv6 address subnet and range identities that can be
891 used as owners of shared secrets.
897 - Properly handle potential EINTR errors in sigwaitinfo(2) calls that replaced
898 sigwait(3) calls with 5.3.4.
900 - RADIUS retransmission timeouts are now configurable, courtesy of Thom Troy.
906 - Fixed an authentication bypass vulnerability in the eap-mschapv2 plugin that
907 was caused by insufficient verification of the internal state when handling
908 MSCHAPv2 Success messages received by the client.
909 This vulnerability has been registered as CVE-2015-8023.
911 - The sha3 plugin implements the SHA3 Keccak-F1600 hash algorithm family.
912 Within the strongSwan framework SHA3 is currently used for BLISS signatures
913 only because the OIDs for other signature algorithms haven't been defined
914 yet. Also the use of SHA3 for IKEv2 has not been standardized yet.
920 - Added support for the ChaCha20/Poly1305 AEAD cipher specified in RFC 7539 and
921 RFC 7634 using the chacha20poly1305 ike/esp proposal keyword. The new chapoly
922 plugin implements the cipher, if possible SSE-accelerated on x86/x64
923 architectures. It is usable both in IKEv2 and the strongSwan libipsec ESP
924 backend. On Linux 4.2 or newer the kernel-netlink plugin can configure the
927 - The vici interface now supports the configuration of auxiliary certification
928 authority information as CRL and OCSP URIs.
930 - In the bliss plugin the c_indices derivation using a SHA-512 based random
931 oracle has been fixed, generalized and standardized by employing the MGF1 mask
932 generation function with SHA-512. As a consequence BLISS signatures using the
933 improved oracle are not compatible with the earlier implementation.
935 - Support for auto=route with right=%any for transport mode connections has
936 been added (the ikev2/trap-any scenario provides examples).
938 - The starter daemon does not flush IPsec policies and SAs anymore when it is
939 stopped. Already existing duplicate policies are now overwritten by the IKE
940 daemon when it installs its policies.
942 - Init limits (like charon.init_limit_half_open) can now optionally be enforced
943 when initiating SAs via VICI. For this, IKE_SAs initiated by the daemon are
944 now also counted as half-open SAs, which, as a side-effect, fixes the status
945 output while connecting (e.g. in ipsec status).
947 - Symmetric configuration of EAP methods in left|rightauth is now possible when
948 mutual EAP-only authentication is used (previously, the client had to
949 configure rightauth=eap or rightauth=any, which prevented it from using this
950 same config as responder).
952 - The initiator flag in the IKEv2 header is compared again (wasn't the case
953 since 5.0.0) and packets that have the flag set incorrectly are again ignored.
955 - Implemented a demo Hardcopy Device IMC/IMV pair based on the "Hardcopy
956 Device Health Assessment Trusted Network Connect Binding" (HCD-TNC)
957 document drafted by the IEEE Printer Working Group (PWG).
959 - Fixed IF-M segmentation which failed in the presence of multiple small
960 attributes in front of a huge attribute to be segmented.
966 - Fixed a vulnerability that allowed rogue servers with a valid certificate
967 accepted by the client to trick it into disclosing its username and even
968 password (if the client accepts EAP-GTC). This was caused because constraints
969 against the responder's authentication were enforced too late.
970 This vulnerability has been registered as CVE-2015-4171.
976 - Fixed a denial-of-service and potential remote code execution vulnerability
977 triggered by IKEv1/IKEv2 messages that contain payloads for the respective
978 other IKE version. Such payload are treated specially since 5.2.2 but because
979 they were still identified by their original payload type they were used as
980 such in some places causing invalid function pointer dereferences.
981 The vulnerability has been registered as CVE-2015-3991.
983 - The new aesni plugin provides CBC, CTR, XCBC, CMAC, CCM and GCM crypto
984 primitives for AES-128/192/256. The plugin requires AES-NI and PCLMULQDQ
985 instructions and works on both x86 and x64 architectures. It provides
986 superior crypto performance in userland without any external libraries.
992 - Added support for IKEv2 make-before-break reauthentication. By using a global
993 CHILD_SA reqid allocation mechanism, charon supports overlapping CHILD_SAs.
994 This allows the use of make-before-break instead of the previously supported
995 break-before-make reauthentication, avoiding connectivity gaps during that
996 procedure. As the new mechanism may fail with peers not supporting it (such
997 as any previous strongSwan release) it must be explicitly enabled using
998 the charon.make_before_break strongswan.conf option.
1000 - Support for "Signature Authentication in IKEv2" (RFC 7427) has been added.
1001 This allows the use of stronger hash algorithms for public key authentication.
1002 By default, signature schemes are chosen based on the strength of the
1003 signature key, but specific hash algorithms may be configured in leftauth.
1005 - Key types and hash algorithms specified in rightauth are now also checked
1006 against IKEv2 signature schemes. If such constraints are used for certificate
1007 chain validation in existing configurations, in particular with peers that
1008 don't support RFC 7427, it may be necessary to disable this feature with the
1009 charon.signature_authentication_constraints setting, because the signature
1010 scheme used in classic IKEv2 public key authentication may not be strong
1013 - The new connmark plugin allows a host to bind conntrack flows to a specific
1014 CHILD_SA by applying and restoring the SA mark to conntrack entries. This
1015 allows a peer to handle multiple transport mode connections coming over the
1016 same NAT device for client-initiated flows. A common use case is to protect
1017 L2TP/IPsec, as supported by some systems.
1019 - The forecast plugin can forward broadcast and multicast messages between
1020 connected clients and a LAN. For CHILD_SA using unique marks, it sets up
1021 the required Netfilter rules and uses a multicast/broadcast listener that
1022 forwards such messages to all connected clients. This plugin is designed for
1023 Windows 7 IKEv2 clients, which announces its services over the tunnel if the
1024 negotiated IPsec policy allows it.
1026 - For the vici plugin a Python Egg has been added to allow Python applications
1027 to control or monitor the IKE daemon using the VICI interface, similar to the
1028 existing ruby gem. The Python library has been contributed by Björn Schuberg.
1030 - EAP server methods now can fulfill public key constraints, such as rightcert
1031 or rightca. Additionally, public key and signature constraints can be
1032 specified for EAP methods in the rightauth keyword. Currently the EAP-TLS and
1033 EAP-TTLS methods provide verification details to constraints checking.
1035 - Upgrade of the BLISS post-quantum signature algorithm to the improved BLISS-B
1036 variant. Can be used in conjunction with the SHA256, SHA384 and SHA512 hash
1037 algorithms with SHA512 being the default.
1039 - The IF-IMV 1.4 interface now makes the IP address of the TNC access requestor
1040 as seen by the TNC server available to all IMVs. This information can be
1041 forwarded to policy enforcement points (e.g. firewalls or routers).
1043 - The new mutual tnccs-20 plugin parameter activates mutual TNC measurements
1044 in PB-TNC half-duplex mode between two endpoints over either a PT-EAP or
1045 PT-TLS transport medium.
1051 - Fixed a denial-of-service vulnerability triggered by an IKEv2 Key Exchange
1052 payload that contains the Diffie-Hellman group 1025. This identifier was
1053 used internally for DH groups with custom generator and prime. Because
1054 these arguments are missing when creating DH objects based on the KE payload
1055 an invalid pointer dereference occurred. This allowed an attacker to crash
1056 the IKE daemon with a single IKE_SA_INIT message containing such a KE
1057 payload. The vulnerability has been registered as CVE-2014-9221.
1059 - The left/rightid options in ipsec.conf, or any other identity in strongSwan,
1060 now accept prefixes to enforce an explicit type, such as email: or fqdn:.
1061 Note that no conversion is done for the remaining string, refer to
1062 ipsec.conf(5) for details.
1064 - The post-quantum Bimodal Lattice Signature Scheme (BLISS) can be used as
1065 an IKEv2 public key authentication method. The pki tool offers full support
1066 for the generation of BLISS key pairs and certificates.
1068 - Fixed mapping of integrity algorithms negotiated for AH via IKEv1. This could
1069 cause interoperability issues when connecting to older versions of charon.
1075 - The new charon-systemd IKE daemon implements an IKE daemon tailored for use
1076 with systemd. It avoids the dependency on ipsec starter and uses swanctl
1077 as configuration backend, building a simple and lightweight solution. It
1078 supports native systemd journal logging.
1080 - Support for IKEv2 fragmentation as per RFC 7383 has been added. Like IKEv1
1081 fragmentation it can be enabled by setting fragmentation=yes in ipsec.conf.
1083 - Support of the TCG TNC IF-M Attribute Segmentation specification proposal.
1084 All attributes can be segmented. Additionally TCG/SWID Tag, TCG/SWID Tag ID
1085 and IETF/Installed Packages attributes can be processed incrementally on a
1088 - The new ext-auth plugin calls an external script to implement custom IKE_SA
1089 authorization logic, courtesy of Vyronas Tsingaras.
1091 - For the vici plugin a ruby gem has been added to allow ruby applications
1092 to control or monitor the IKE daemon. The vici documentation has been updated
1093 to include a description of the available operations and some simple examples
1094 using both the libvici C interface and the ruby gem.
1100 - strongSwan has been ported to the Windows platform. Using a MinGW toolchain,
1101 many parts of the strongSwan codebase run natively on Windows 7 / 2008 R2
1102 and newer releases. charon-svc implements a Windows IKE service based on
1103 libcharon, the kernel-iph and kernel-wfp plugins act as networking and IPsec
1104 backend on the Windows platform. socket-win provides a native IKE socket
1105 implementation, while winhttp fetches CRL and OCSP information using the
1108 - The new vici plugin provides a Versatile IKE Configuration Interface for
1109 charon. Using the stable IPC interface, external applications can configure,
1110 control and monitor the IKE daemon. Instead of scripting the ipsec tool
1111 and generating ipsec.conf, third party applications can use the new interface
1112 for more control and better reliability.
1114 - Built upon the libvici client library, swanctl implements the first user of
1115 the VICI interface. Together with a swanctl.conf configuration file,
1116 connections can be defined, loaded and managed. swanctl provides a portable,
1117 complete IKE configuration and control interface for the command line.
1118 The first six swanctl example scenarios have been added.
1120 - The SWID IMV implements a JSON-based REST API which allows the exchange
1121 of SWID tags and Software IDs with the strongTNC policy manager.
1123 - The SWID IMC can extract all installed packages from the dpkg (Debian,
1124 Ubuntu, Linux Mint etc.), rpm (Fedora, RedHat, OpenSUSE, etc.), or
1125 pacman (Arch Linux, Manjaro, etc.) package managers, respectively, using the
1126 swidGenerator (https://github.com/strongswan/swidGenerator) which generates
1127 SWID tags according to the new ISO/IEC 19770-2:2014 standard.
1129 - All IMVs now share the access requestor ID, device ID and product info
1130 of an access requestor via a common imv_session object.
1132 - The Attestation IMC/IMV pair supports the IMA-NG measurement format
1133 introduced with the Linux 3.13 kernel.
1135 - The aikgen tool generates an Attestation Identity Key bound to a TPM.
1137 - Implemented the PT-EAP transport protocol (RFC 7171) for Trusted Network
1140 - The ipsec.conf replay_window option defines connection specific IPsec replay
1141 windows. Original patch courtesy of Zheng Zhong and Christophe Gouault from
1148 - Fixed an authentication bypass vulnerability triggered by rekeying an
1149 unestablished IKEv2 SA while it gets actively initiated. This allowed an
1150 attacker to trick a peer's IKE_SA state to established, without the need to
1151 provide any valid authentication credentials. The vulnerability has been
1152 registered as CVE-2014-2338.
1154 - The acert plugin evaluates X.509 Attribute Certificates. Group membership
1155 information encoded as strings can be used to fulfill authorization checks
1156 defined with the rightgroups option. Attribute Certificates can be loaded
1157 locally or get exchanged in IKEv2 certificate payloads.
1159 - The pki command gained support to generate X.509 Attribute Certificates
1160 using the --acert subcommand, while the --print command supports the ac type.
1161 The openac utility has been removed in favor of the new pki functionality.
1163 - The libtls TLS 1.2 implementation as used by EAP-(T)TLS and other protocols
1164 has been extended by AEAD mode support, currently limited to AES-GCM.
1170 - A new default configuration file layout is introduced. The new default
1171 strongswan.conf file mainly includes config snippets from the strongswan.d
1172 and strongswan.d/charon directories (the latter containing snippets for all
1173 plugins). The snippets, with commented defaults, are automatically
1174 generated and installed, if they don't exist yet. They are also installed
1175 in $prefix/share/strongswan/templates so existing files can be compared to
1176 the current defaults.
1178 - As an alternative to the non-extensible charon.load setting, the plugins
1179 to load in charon (and optionally other applications) can now be determined
1180 via the charon.plugins.<name>.load setting for each plugin (enabled in the
1181 new default strongswan.conf file via the charon.load_modular option).
1182 The load setting optionally takes a numeric priority value that allows
1183 reordering the plugins (otherwise the default plugin order is preserved).
1185 - All strongswan.conf settings that were formerly defined in library specific
1186 "global" sections are now application specific (e.g. settings for plugins in
1187 libstrongswan.plugins can now be set only for charon in charon.plugins).
1188 The old options are still supported, which now allows to define defaults for
1189 all applications in the libstrongswan section.
1191 - The ntru libstrongswan plugin supports NTRUEncrypt as a post-quantum
1192 computer IKE key exchange mechanism. The implementation is based on the
1193 ntru-crypto library from the NTRUOpenSourceProject. The supported security
1194 strengths are ntru112, ntru128, ntru192, and ntru256. Since the private DH
1195 group IDs 1030..1033 have been assigned, the strongSwan Vendor ID must be
1196 sent (charon.send_vendor_id = yes) in order to use NTRU.
1198 - Defined a TPMRA remote attestation workitem and added support for it to the
1201 - Compatibility issues between IPComp (compress=yes) and leftfirewall=yes as
1202 well as multiple subnets in left|rightsubnet have been fixed.
1204 - When enabling its "session" strongswan.conf option, the xauth-pam plugin opens
1205 and closes a PAM session for each established IKE_SA. Patch courtesy of
1208 - The strongSwan unit testing framework has been rewritten without the "check"
1209 dependency for improved flexibility and portability. It now properly supports
1210 multi-threaded and memory leak testing and brings a bunch of new test cases.
1216 - Fixed a denial-of-service vulnerability and potential authorization bypass
1217 triggered by a crafted ID_DER_ASN1_DN ID payload. The cause is an insufficient
1218 length check when comparing such identities. The vulnerability has been
1219 registered as CVE-2013-6075.
1221 - Fixed a denial-of-service vulnerability triggered by a crafted IKEv1
1222 fragmentation payload. The cause is a NULL pointer dereference. The
1223 vulnerability has been registered as CVE-2013-6076.
1225 - The lean stand-alone pt-tls-client can set up a RFC 6876 PT-TLS session
1226 with a strongSwan policy enforcement point which uses the tnc-pdp charon
1229 - The new TCG TNC SWID IMC/IMV pair supports targeted SWID requests for either
1230 full SWID Tag or concise SWID Tag ID inventories.
1232 - The XAuth backend in eap-radius now supports multiple XAuth exchanges for
1233 different credential types and display messages. All user input gets
1234 concatenated and verified with a single User-Password RADIUS attribute on
1235 the AAA. With an AAA supporting it, one for example can implement
1236 Password+Token authentication with proper dialogs on iOS and OS X clients.
1238 - charon supports IKEv1 Mode Config exchange in push mode. The ipsec.conf
1239 modeconfig=push option enables it for both client and server, the same way
1242 - Using the "ah" ipsec.conf keyword on both IKEv1 and IKEv2 connections,
1243 charon can negotiate and install Security Associations integrity-protected by
1244 the Authentication Header protocol. Supported are plain AH(+IPComp) SAs only,
1245 but not the deprecated RFC2401 style ESP+AH bundles.
1247 - The generation of initialization vectors for IKE and ESP (when using libipsec)
1248 is now modularized and IVs for e.g. AES-GCM are now correctly allocated
1249 sequentially, while other algorithms like AES-CBC still use random IVs.
1251 - The left and right options in ipsec.conf can take multiple address ranges
1252 and subnets. This allows connection matching against a larger set of
1253 addresses, for example to use a different connection for clients connecting
1254 from a internal network.
1256 - For all those who have a queasy feeling about the NIST elliptic curve set,
1257 the Brainpool curves introduced for use with IKE by RFC 6932 might be a
1258 more trustworthy alternative.
1260 - The kernel-libipsec userland IPsec backend now supports usage statistics,
1261 volume based rekeying and accepts ESPv3 style TFC padded packets.
1263 - With two new strongswan.conf options fwmarks can be used to implement
1264 host-to-host tunnels with kernel-libipsec.
1266 - load-tester supports transport mode connections and more complex traffic
1267 selectors, including such using unique ports for each tunnel.
1269 - The new dnscert plugin provides support for authentication via CERT RRs that
1270 are protected via DNSSEC. The plugin was created by Ruslan N. Marchenko.
1272 - The eap-radius plugin supports forwarding of several Cisco Unity specific
1273 RADIUS attributes in corresponding configuration payloads.
1275 - Database transactions are now abstracted and implemented by the two backends.
1276 If you use MySQL make sure all tables use the InnoDB engine.
1278 - libstrongswan now can provide an experimental custom implementation of the
1279 printf family functions based on klibc if neither Vstr nor glibc style printf
1280 hooks are available. This can avoid the Vstr dependency on some systems at
1281 the cost of slower and less complete printf functions.
1287 - Fixed a denial-of-service vulnerability triggered by specific XAuth usernames
1288 and EAP identities (since 5.0.3), and PEM files (since 4.1.11). The crash
1289 was caused by insufficient error handling in the is_asn1() function.
1290 The vulnerability has been registered as CVE-2013-5018.
1292 - The new charon-cmd command line IKE client can establish road warrior
1293 connections using IKEv1 or IKEv2 with different authentication profiles.
1294 It does not depend on any configuration files and can be configured using a
1295 few simple command line options.
1297 - The kernel-pfroute networking backend has been greatly improved. It now
1298 can install virtual IPs on TUN devices on OS X and FreeBSD, allowing these
1299 systems to act as a client in common road warrior scenarios.
1301 - The new kernel-libipsec plugin uses TUN devices and libipsec to provide IPsec
1302 processing in userland on Linux, FreeBSD and Mac OS X.
1304 - The eap-radius plugin can now serve as an XAuth backend called xauth-radius,
1305 directly verifying XAuth credentials using RADIUS User-Name/User-Password
1306 attributes. This is more efficient than the existing xauth-eap+eap-radius
1307 combination, and allows RADIUS servers without EAP support to act as AAA
1310 - The new osx-attr plugin installs configuration attributes (currently DNS
1311 servers) via SystemConfiguration on Mac OS X. The keychain plugin provides
1312 certificates from the OS X keychain service.
1314 - The sshkey plugin parses SSH public keys, which, together with the --agent
1315 option for charon-cmd, allows the use of ssh-agent for authentication.
1316 To configure SSH keys in ipsec.conf the left|rightrsasigkey options are
1317 replaced with left|rightsigkey, which now take public keys in one of three
1318 formats: SSH (RFC 4253, ssh: prefix), DNSKEY (RFC 3110, dns: prefix), and
1319 PKCS#1 (the default, no prefix).
1321 - Extraction of certificates and private keys from PKCS#12 files is now provided
1322 by the new pkcs12 plugin or the openssl plugin. charon-cmd (--p12) as well
1323 as charon (via P12 token in ipsec.secrets) can make use of this.
1325 - IKEv2 can now negotiate transport mode and IPComp in NAT situations.
1327 - IKEv2 exchange initiators now properly close an established IKE or CHILD_SA
1328 on error conditions using an additional exchange, keeping state in sync
1331 - Using a SQL database interface a Trusted Network Connect (TNC) Policy Manager
1332 can generate specific measurement workitems for an arbitrary number of
1333 Integrity Measurement Verifiers (IMVs) based on the history of the VPN user
1336 - Several core classes in libstrongswan are now tested with unit tests. These
1337 can be enabled with --enable-unit-tests and run with 'make check'. Coverage
1338 reports can be generated with --enable-coverage and 'make coverage' (this
1339 disables any optimization, so it should not be enabled when building
1340 production releases).
1342 - The leak-detective developer tool has been greatly improved. It works much
1343 faster/stabler with multiple threads, does not use deprecated malloc hooks
1344 anymore and has been ported to OS X.
1346 - chunk_hash() is now based on SipHash-2-4 with a random key. This provides
1347 better distribution and prevents hash flooding attacks when used with
1350 - All default plugins implement the get_features() method to define features
1351 and their dependencies. The plugin loader has been improved, so that plugins
1352 in a custom load statement can be ordered freely or to express preferences
1353 without being affected by dependencies between plugin features.
1355 - A centralized thread can take care for watching multiple file descriptors
1356 concurrently. This removes the need for a dedicated listener threads in
1357 various plugins. The number of "reserved" threads for such tasks has been
1358 reduced to about five, depending on the plugin configuration.
1360 - Plugins that can be controlled by a UNIX socket IPC mechanism gained network
1361 transparency. Third party applications querying these plugins now can use
1362 TCP connections from a different host.
1364 - libipsec now supports AES-GCM.
1370 - Fixed a security vulnerability in the openssl plugin which was reported by
1371 Kevin Wojtysiak. The vulnerability has been registered as CVE-2013-2944.
1372 Before the fix, if the openssl plugin's ECDSA signature verification was used,
1373 due to a misinterpretation of the error code returned by the OpenSSL
1374 ECDSA_verify() function, an empty or zeroed signature was accepted as a
1377 - The handling of a couple of other non-security relevant openssl return codes
1380 - The tnc_ifmap plugin now publishes virtual IPv4 and IPv6 addresses via its
1381 TCG TNC IF-MAP 2.1 interface.
1383 - The charon.initiator_only option causes charon to ignore IKE initiation
1386 - The openssl plugin can now use the openssl-fips library.
1392 - The new ipseckey plugin enables authentication based on trustworthy public
1393 keys stored as IPSECKEY resource records in the DNS and protected by DNSSEC.
1394 To do so it uses a DNSSEC enabled resolver, like the one provided by the new
1395 unbound plugin, which is based on libldns and libunbound. Both plugins were
1396 created by Reto Guadagnini.
1398 - Implemented the TCG TNC IF-IMV 1.4 draft making access requestor identities
1399 available to an IMV. The OS IMV stores the AR identity together with the
1400 device ID in the attest database.
1402 - The openssl plugin now uses the AES-NI accelerated version of AES-GCM
1403 if the hardware supports it.
1405 - The eap-radius plugin can now assign virtual IPs to IKE clients using the
1406 Framed-IP-Address attribute by using the "%radius" named pool in the
1407 rightsourceip ipsec.conf option. Cisco Banner attributes are forwarded to
1408 Unity-capable IKEv1 clients during mode config. charon now sends Interim
1409 Accounting updates if requested by the RADIUS server, reports
1410 sent/received packets in Accounting messages, and adds a Terminate-Cause
1411 to Accounting-Stops.
1413 - The recently introduced "ipsec listcounters" command can report connection
1414 specific counters by passing a connection name, and global or connection
1415 counters can be reset by the "ipsec resetcounters" command.
1417 - The strongSwan libpttls library provides an experimental implementation of
1418 PT-TLS (RFC 6876), a Posture Transport Protocol over TLS.
1420 - The charon systime-fix plugin can disable certificate lifetime checks on
1421 embedded systems if the system time is obviously out of sync after bootup.
1422 Certificates lifetimes get checked once the system time gets sane, closing
1423 or reauthenticating connections using expired certificates.
1425 - The "ikedscp" ipsec.conf option can set DiffServ code points on outgoing
1428 - The new xauth-noauth plugin allows to use basic RSA or PSK authentication with
1429 clients that cannot be configured without XAuth authentication. The plugin
1430 simply concludes the XAuth exchange successfully without actually performing
1431 any authentication. Therefore, to use this backend it has to be selected
1432 explicitly with rightauth2=xauth-noauth.
1434 - The new charon-tkm IKEv2 daemon delegates security critical operations to a
1435 separate process. This has the benefit that the network facing daemon has no
1436 knowledge of keying material used to protect child SAs. Thus subverting
1437 charon-tkm does not result in the compromise of cryptographic keys.
1438 The extracted functionality has been implemented from scratch in a minimal TCB
1439 (trusted computing base) in the Ada programming language. Further information
1440 can be found at https://www.codelabs.ch/tkm/.
1445 - Implemented all IETF Standard PA-TNC attributes and an OS IMC/IMV
1446 pair using them to transfer operating system information.
1448 - The new "ipsec listcounters" command prints a list of global counter values
1449 about received and sent IKE messages and rekeyings.
1451 - A new lookip plugin can perform fast lookup of tunnel information using a
1452 clients virtual IP and can send notifications about established or deleted
1453 tunnels. The "ipsec lookip" command can be used to query such information
1454 or receive notifications.
1456 - The new error-notify plugin catches some common error conditions and allows
1457 an external application to receive notifications for them over a UNIX socket.
1459 - IKE proposals can now use a PRF algorithm different to that defined for
1460 integrity protection. If an algorithm with a "prf" prefix is defined
1461 explicitly (such as prfsha1 or prfsha256), no implicit PRF algorithm based on
1462 the integrity algorithm is added to the proposal.
1464 - The pkcs11 plugin can now load leftcert certificates from a smartcard for a
1465 specific ipsec.conf conn section and cacert CA certificates for a specific ca
1468 - The load-tester plugin gained additional options for certificate generation
1469 and can load keys and multiple CA certificates from external files. It can
1470 install a dedicated outer IP address for each tunnel and tunnel initiation
1471 batches can be triggered and monitored externally using the
1472 "ipsec load-tester" tool.
1474 - PKCS#7 container parsing has been modularized, and the openssl plugin
1475 gained an alternative implementation to decrypt and verify such files.
1476 In contrast to our own DER parser, OpenSSL can handle BER files, which is
1477 required for interoperability of our scepclient with EJBCA.
1479 - Support for the proprietary IKEv1 fragmentation extension has been added.
1480 Fragments are always handled on receipt but only sent if supported by the peer
1481 and if enabled with the new fragmentation ipsec.conf option.
1483 - IKEv1 in charon can now parse certificates received in PKCS#7 containers and
1484 supports NAT traversal as used by Windows clients. Patches courtesy of
1487 - The new rdrand plugin provides a high quality / high performance random
1488 source using the Intel rdrand instruction found on Ivy Bridge processors.
1490 - The integration test environment was updated and now uses KVM and reproducible
1491 guest images based on Debian.
1497 - Introduced the sending of the standard IETF Assessment Result
1498 PA-TNC attribute by all strongSwan Integrity Measurement Verifiers.
1500 - Extended PTS Attestation IMC/IMV pair to provide full evidence of
1501 the Linux IMA measurement process. All pertinent file information
1502 of a Linux OS can be collected and stored in an SQL database.
1504 - The PA-TNC and PB-TNC protocols can now process huge data payloads
1505 >64 kB by distributing PA-TNC attributes over multiple PA-TNC messages
1506 and these messages over several PB-TNC batches. As long as no
1507 consolidated recommendation from all IMVs can be obtained, the TNC
1508 server requests more client data by sending an empty SDATA batch.
1510 - The rightgroups2 ipsec.conf option can require group membership during
1511 a second authentication round, for example during XAuth authentication
1512 against a RADIUS server.
1514 - The xauth-pam backend can authenticate IKEv1 XAuth and Hybrid authenticated
1515 clients against any PAM service. The IKEv2 eap-gtc plugin does not use
1516 PAM directly anymore, but can use any XAuth backend to verify credentials,
1517 including xauth-pam.
1519 - The new unity plugin brings support for some parts of the IKEv1 Cisco Unity
1520 Extension. As client, charon narrows traffic selectors to the received
1521 Split-Include attributes and automatically installs IPsec bypass policies
1522 for received Local-LAN attributes. As server, charon sends Split-Include
1523 attributes for leftsubnet definitions containing multiple subnets to Unity-
1526 - An EAP-Nak payload is returned by clients if the gateway requests an EAP
1527 method that the client does not support. Clients can also request a specific
1528 EAP method by configuring that method with leftauth.
1530 - The eap-dynamic plugin handles EAP-Nak payloads returned by clients and uses
1531 these to select a different EAP method supported/requested by the client.
1532 The plugin initially requests the first registered method or the first method
1533 configured with charon.plugins.eap-dynamic.preferred.
1535 - The new left/rightdns options specify connection specific DNS servers to
1536 request/respond in IKEv2 configuration payloads or IKEv2 mode config. leftdns
1537 can be any (comma separated) combination of %config4 and %config6 to request
1538 multiple servers, both for IPv4 and IPv6. rightdns takes a list of DNS server
1539 IP addresses to return.
1541 - The left/rightsourceip options now accept multiple addresses or pools.
1542 leftsourceip can be any (comma separated) combination of %config4, %config6
1543 or fixed IP addresses to request. rightsourceip accepts multiple explicitly
1544 specified or referenced named pools.
1546 - Multiple connections can now share a single address pool when they use the
1547 same definition in one of the rightsourceip pools.
1549 - The options charon.interfaces_ignore and charon.interfaces_use allow one to
1550 configure the network interfaces used by the daemon.
1552 - The kernel-netlink plugin supports the charon.install_virtual_ip_on option,
1553 which specifies the interface on which virtual IP addresses will be installed.
1554 If it is not specified the current behavior of using the outbound interface
1557 - The kernel-netlink plugin tries to keep the current source address when
1558 looking for valid routes to reach other hosts.
1560 - The autotools build has been migrated to use a config.h header. strongSwan
1561 development headers will get installed during "make install" if
1562 --with-dev-headers has been passed to ./configure.
1564 - All crypto primitives gained return values for most operations, allowing
1565 crypto backends to fail, for example when using hardware accelerators.
1571 - The charon IKE daemon gained experimental support for the IKEv1 protocol.
1572 Pluto has been removed from the 5.x series, and unless strongSwan is
1573 configured with --disable-ikev1 or --disable-ikev2, charon handles both
1574 keying protocols. The feature-set of IKEv1 in charon is almost on par with
1575 pluto, but currently does not support AH or bundled AH+ESP SAs. Beside
1576 RSA/ECDSA, PSK and XAuth, charon also supports the Hybrid authentication
1577 mode. Information for interoperability and migration is available at
1578 https://wiki.strongswan.org/projects/strongswan/wiki/CharonPlutoIKEv1.
1580 - Charon's bus_t has been refactored so that loggers and other listeners are
1581 now handled separately. The single lock was previously cause for deadlocks
1582 if extensive listeners, such as the one provided by the updown plugin, wanted
1583 to acquire locks that were held by other threads which in turn tried to log
1584 messages, and thus were waiting to acquire the same lock currently held by
1585 the thread calling the listener.
1586 The implemented changes also allow the use of a read/write-lock for the
1587 loggers which increases performance if multiple loggers are registered.
1588 Besides several interface changes this last bit also changes the semantics
1589 for loggers as these may now be called by multiple threads at the same time.
1591 - Source routes are reinstalled if interfaces are reactivated or IP addresses
1594 - The thread pool (processor_t) now has more control over the lifecycle of
1595 a job (see job.h for details). In particular, it now controls the destruction
1596 of jobs after execution and the cancellation of jobs during shutdown. Due to
1597 these changes the requeueing feature, previously available to callback_job_t
1598 only, is now available to all jobs (in addition to a new rescheduling
1601 - In addition to trustchain key strength definitions for different public key
1602 systems, the rightauth option now takes a list of signature hash algorithms
1603 considered save for trustchain validation. For example, the setting
1604 rightauth=rsa-2048-ecdsa-256-sha256-sha384-sha512 requires a trustchain
1605 that uses at least RSA-2048 or ECDSA-256 keys and certificate signatures
1606 using SHA-256 or better.
1612 - Fixed a security vulnerability in the gmp plugin. If this plugin was used
1613 for RSA signature verification an empty or zeroed signature was handled as
1616 - Fixed several issues with reauthentication and address updates.
1622 - The tnc-pdp plugin implements a RADIUS server interface allowing
1623 a strongSwan TNC server to act as a Policy Decision Point.
1625 - The eap-radius authentication backend enforces Session-Timeout attributes
1626 using RFC4478 repeated authentication and acts upon RADIUS Dynamic
1627 Authorization extensions, RFC 5176. Currently supported are disconnect
1628 requests and CoA messages containing a Session-Timeout.
1630 - The eap-radius plugin can forward arbitrary RADIUS attributes from and to
1631 clients using custom IKEv2 notify payloads. The new radattr plugin reads
1632 attributes to include from files and prints received attributes to the
1635 - Added support for untruncated MD5 and SHA1 HMACs in ESP as used in
1638 - The cmac plugin implements the AES-CMAC-96 and AES-CMAC-PRF-128 algorithms
1639 as defined in RFC 4494 and RFC 4615, respectively.
1641 - The resolve plugin automatically installs nameservers via resolvconf(8),
1642 if it is installed, instead of modifying /etc/resolv.conf directly.
1644 - The IKEv2 charon daemon supports now raw RSA public keys in RFC 3110
1645 DNSKEY and PKCS#1 file format.
1651 - Upgraded the TCG IF-IMC and IF-IMV C API to the upcoming version 1.3
1652 which supports IF-TNCCS 2.0 long message types, the exclusive flags
1653 and multiple IMC/IMV IDs. Both the TNC Client and Server as well as
1654 the "Test", "Scanner", and "Attestation" IMC/IMV pairs were updated.
1656 - Fully implemented the "TCG Attestation PTS Protocol: Binding to IF-M"
1657 standard (TLV-based messages only). TPM-based remote attestation of
1658 Linux IMA (Integrity Measurement Architecture) possible. Measurement
1659 reference values are automatically stored in an SQLite database.
1661 - The EAP-RADIUS authentication backend supports RADIUS accounting. It sends
1662 start/stop messages containing Username, Framed-IP and Input/Output-Octets
1663 attributes and has been tested against FreeRADIUS and Microsoft NPS.
1665 - Added support for PKCS#8 encoded private keys via the libstrongswan
1666 pkcs8 plugin. This is the default format used by some OpenSSL tools since
1667 version 1.0.0 (e.g. openssl req with -keyout).
1669 - Added session resumption support to the strongSwan TLS stack.
1675 - Because of changing checksums before and after installation which caused
1676 the integrity tests to fail we avoided directly linking libsimaka, libtls and
1677 libtnccs to those libcharon plugins which make use of these dynamic libraries.
1678 Instead we linked the libraries to the charon daemon. Unfortunately Ubuntu
1679 11.10 activated the --as-needed ld option which discards explicit links
1680 to dynamic libraries that are not actually used by the charon daemon itself,
1681 thus causing failures during the loading of the plugins which depend on these
1682 libraries for resolving external symbols.
1684 - Therefore our approach of computing integrity checksums for plugins had to be
1685 changed radically by moving the hash generation from the compilation to the
1686 post-installation phase.
1692 - The new libstrongswan certexpire plugin collects expiration information of
1693 all used certificates and exports them to CSV files. It either directly
1694 exports them or uses cron style scheduling for batch exports.
1696 - starter passes unresolved hostnames to charon, allowing it to do name
1697 resolution not before the connection attempt. This is especially useful with
1698 connections between hosts using dynamic IP addresses. Thanks to Mirko Parthey
1699 for the initial patch.
1701 - The android plugin can now be used without the Android frontend patch and
1702 provides DNS server registration and logging to logcat.
1704 - Pluto and starter (plus stroke and whack) have been ported to Android.
1706 - Support for ECDSA private and public key operations has been added to the
1707 pkcs11 plugin. The plugin now also provides DH and ECDH via PKCS#11 and can
1708 use tokens as random number generators (RNG). By default only private key
1709 operations are enabled, more advanced features have to be enabled by their
1710 option in strongswan.conf. This also applies to public key operations (even
1711 for keys not stored on the token) which were enabled by default before.
1713 - The libstrongswan plugin system now supports detailed plugin dependencies.
1714 Many plugins have been extended to export its capabilities and requirements.
1715 This allows the plugin loader to resolve plugin loading order automatically,
1716 and in future releases, to dynamically load the required features on demand.
1717 Existing third party plugins are source (but not binary) compatible if they
1718 properly initialize the new get_features() plugin function to NULL.
1720 - The tnc-ifmap plugin implements a TNC IF-MAP 2.0 client which can deliver
1721 metadata about IKE_SAs via a SOAP interface to a MAP server. The tnc-ifmap
1722 plugin requires the Apache Axis2/C library.
1728 - Our private libraries (e.g. libstrongswan) are not installed directly in
1729 prefix/lib anymore. Instead a subdirectory is used (prefix/lib/ipsec/ by
1730 default). The plugins directory is also moved from libexec/ipsec/ to that
1733 - The dynamic IMC/IMV libraries were moved from the plugins directory to
1734 a new imcvs directory in the prefix/lib/ipsec/ subdirectory.
1736 - Job priorities were introduced to prevent thread starvation caused by too
1737 many threads handling blocking operations (such as CRL fetching). Refer to
1738 strongswan.conf(5) for details.
1740 - Two new strongswan.conf options allow to fine-tune performance on IKEv2
1741 gateways by dropping IKE_SA_INIT requests on high load.
1743 - IKEv2 charon daemon supports start PASS and DROP shunt policies
1744 preventing traffic to go through IPsec connections. Installation of the
1745 shunt policies either via the XFRM netfilter or PFKEYv2 IPsec kernel
1748 - The history of policies installed in the kernel is now tracked so that e.g.
1749 trap policies are correctly updated when reauthenticated SAs are terminated.
1751 - IMC/IMV Scanner pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1752 Using "netstat -l" the IMC scans open listening ports on the TNC client
1753 and sends a port list to the IMV which based on a port policy decides if
1754 the client is admitted to the network.
1755 (--enable-imc-scanner/--enable-imv-scanner).
1757 - IMC/IMV Test pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1758 (--enable-imc-test/--enable-imv-test).
1760 - The IKEv2 close action does not use the same value as the ipsec.conf dpdaction
1761 setting, but the value defined by its own closeaction keyword. The action
1762 is triggered if the remote peer closes a CHILD_SA unexpectedly.
1768 - The whitelist plugin for the IKEv2 daemon maintains an in-memory identity
1769 whitelist. Any connection attempt of peers not whitelisted will get rejected.
1770 The 'ipsec whitelist' utility provides a simple command line frontend for
1771 whitelist administration.
1773 - The duplicheck plugin provides a specialized form of duplicate checking,
1774 doing a liveness check on the old SA and optionally notify a third party
1775 application about detected duplicates.
1777 - The coupling plugin permanently couples two or more devices by limiting
1778 authentication to previously used certificates.
1780 - In the case that the peer config and child config don't have the same name
1781 (usually in SQL database defined connections), ipsec up|route <peer config>
1782 starts|routes all associated child configs and ipsec up|route <child config>
1783 only starts|routes the specific child config.
1785 - fixed the encoding and parsing of X.509 certificate policy statements (CPS).
1787 - Duncan Salerno contributed the eap-sim-pcsc plugin implementing a
1788 pcsc-lite based SIM card backend.
1790 - The eap-peap plugin implements the EAP PEAP protocol. Interoperates
1791 successfully with a FreeRADIUS server and Windows 7 Agile VPN clients.
1793 - The IKEv2 daemon charon rereads strongswan.conf on SIGHUP and instructs
1794 all plugins to reload. Currently only the eap-radius and the attr plugins
1795 support configuration reloading.
1797 - Added userland support to the IKEv2 daemon for Extended Sequence Numbers
1798 support coming with Linux 2.6.39. To enable ESN on a connection, add
1799 the 'esn' keyword to the proposal. The default proposal uses 32-bit sequence
1800 numbers only ('noesn'), and the same value is used if no ESN mode is
1801 specified. To negotiate ESN support with the peer, include both, e.g.
1802 esp=aes128-sha1-esn-noesn.
1804 - In addition to ESN, Linux 2.6.39 gained support for replay windows larger
1805 than 32 packets. The new global strongswan.conf option 'charon.replay_window'
1806 configures the size of the replay window, in packets.
1812 - Sansar Choinyambuu implemented the RFC 5793 Posture Broker Protocol (BP)
1813 compatible with Trusted Network Connect (TNC). The TNCCS 2.0 protocol
1814 requires the tnccs_20, tnc_imc and tnc_imv plugins but does not depend
1815 on the libtnc library. Any available IMV/IMC pairs conforming to the
1816 Trusted Computing Group's TNC-IF-IMV/IMC 1.2 interface specification
1817 can be loaded via /etc/tnc_config.
1819 - Re-implemented the TNCCS 1.1 protocol by using the tnc_imc and tnc_imv
1820 in place of the external libtnc library.
1822 - The tnccs_dynamic plugin loaded on a TNC server in addition to the
1823 tnccs_11 and tnccs_20 plugins, dynamically detects the IF-TNCCS
1824 protocol version used by a TNC client and invokes an instance of
1825 the corresponding protocol stack.
1827 - IKE and ESP proposals can now be stored in an SQL database using a
1828 new proposals table. The start_action field in the child_configs
1829 tables allows the automatic starting or routing of connections stored
1832 - The new certificate_authorities and certificate_distribution_points
1833 tables make it possible to store CRL and OCSP Certificate Distribution
1834 points in an SQL database.
1836 - The new 'include' statement allows to recursively include other files in
1837 strongswan.conf. Existing sections and values are thereby extended and
1838 replaced, respectively.
1840 - Due to the changes in the parser for strongswan.conf, the configuration
1841 syntax for the attr plugin has changed. Previously, it was possible to
1842 specify multiple values of a specific attribute type by adding multiple
1843 key/value pairs with the same key (e.g. dns) to the plugins.attr section.
1844 Because values with the same key now replace previously defined values
1845 this is not possible anymore. As an alternative, multiple values can be
1846 specified by separating them with a comma (e.g. dns = 1.2.3.4, 2.3.4.5).
1848 - ipsec listalgs now appends (set in square brackets) to each crypto
1849 algorithm listed the plugin that registered the function.
1851 - Traffic Flow Confidentiality padding supported with Linux 2.6.38 can be used
1852 by the IKEv2 daemon. The ipsec.conf 'tfc' keyword pads all packets to a given
1853 boundary, the special value '%mtu' pads all packets to the path MTU.
1855 - The new af-alg plugin can use various crypto primitives of the Linux Crypto
1856 API using the AF_ALG interface introduced with 2.6.38. This removes the need
1857 for additional userland implementations of symmetric cipher, hash, hmac and
1860 - The IKEv2 daemon supports the INITIAL_CONTACT notify as initiator and
1861 responder. The notify is sent when initiating configurations with a unique
1862 policy, set in ipsec.conf via the global 'uniqueids' option.
1864 - The conftest conformance testing framework enables the IKEv2 stack to perform
1865 many tests using a distinct tool and configuration frontend. Various hooks
1866 can alter reserved bits, flags, add custom notifies and proposals, reorder
1867 or drop messages and much more. It is enabled using the --enable-conftest
1870 - The new libstrongswan constraints plugin provides advanced X.509 constraint
1871 checking. In addition to X.509 pathLen constraints, the plugin checks for
1872 nameConstraints and certificatePolicies, including policyMappings and
1873 policyConstraints. The x509 certificate plugin and the pki tool have been
1874 enhanced to support these extensions. The new left/rightcertpolicy ipsec.conf
1875 connection keywords take OIDs a peer certificate must have.
1877 - The left/rightauth ipsec.conf keywords accept values with a minimum strength
1878 for trustchain public keys in bits, such as rsa-2048 or ecdsa-256.
1880 - The revocation and x509 libstrongswan plugins and the pki tool gained basic
1881 support for delta CRLs.
1887 - IMPORTANT: the default keyexchange mode 'ike' is changing with release 4.5
1888 from 'ikev1' to 'ikev2', thus commemorating the five year anniversary of the
1889 IKEv2 RFC 4306 and its mature successor RFC 5996. The time has definitively
1890 come for IKEv1 to go into retirement and to cede its place to the much more
1891 robust, powerful and versatile IKEv2 protocol!
1893 - Added new ctr, ccm and gcm plugins providing Counter, Counter with CBC-MAC
1894 and Galois/Counter Modes based on existing CBC implementations. These
1895 new plugins bring support for AES and Camellia Counter and CCM algorithms
1896 and the AES GCM algorithms for use in IKEv2.
1898 - The new pkcs11 plugin brings full Smartcard support to the IKEv2 daemon and
1899 the pki utility using one or more PKCS#11 libraries. It currently supports
1900 RSA private and public key operations and loads X.509 certificates from
1903 - Implemented a general purpose TLS stack based on crypto and credential
1904 primitives of libstrongswan. libtls supports TLS versions 1.0, 1.1 and 1.2,
1905 ECDHE-ECDSA/RSA, DHE-RSA and RSA key exchange algorithms and RSA/ECDSA based
1906 client authentication.
1908 - Based on libtls, the eap-tls plugin brings certificate based EAP
1909 authentication for client and server. It is compatible to Windows 7 IKEv2
1910 Smartcard authentication and the OpenSSL based FreeRADIUS EAP-TLS backend.
1912 - Implemented the TNCCS 1.1 Trusted Network Connect protocol using the
1913 libtnc library on the strongSwan client and server side via the tnccs_11
1914 plugin and optionally connecting to a TNC@FHH-enhanced FreeRADIUS AAA server.
1915 Depending on the resulting TNC Recommendation, strongSwan clients are granted
1916 access to a network behind a strongSwan gateway (allow), are put into a
1917 remediation zone (isolate) or are blocked (none), respectively. Any number
1918 of Integrity Measurement Collector/Verifier pairs can be attached
1919 via the tnc-imc and tnc-imv charon plugins.
1921 - The IKEv1 daemon pluto now uses the same kernel interfaces as the IKEv2
1922 daemon charon. As a result of this, pluto now supports xfrm marks which
1923 were introduced in charon with 4.4.1.
1925 - Applets for Maemo 5 (Nokia) allow to easily configure and control IKEv2
1926 based VPN connections with EAP authentication on supported devices.
1928 - The RADIUS plugin eap-radius now supports multiple RADIUS servers for
1929 redundant setups. Servers are selected by a defined priority, server load and
1932 - The simple led plugin controls hardware LEDs through the Linux LED subsystem.
1933 It currently shows activity of the IKE daemon and is a good example how to
1934 implement a simple event listener.
1936 - Improved MOBIKE behavior in several corner cases, for instance, if the
1937 initial responder moves to a different address.
1939 - Fixed left-/rightnexthop option, which was broken since 4.4.0.
1941 - Fixed a bug not releasing a virtual IP address to a pool if the XAUTH
1942 identity was different from the IKE identity.
1944 - Fixed the alignment of ModeConfig messages on 4-byte boundaries in the
1945 case where the attributes are not a multiple of 4 bytes (e.g. Cisco's
1948 - Fixed the interoperability of the socket_raw and socket_default
1951 - Added man page for strongswan.conf
1957 - Support of xfrm marks in IPsec SAs and IPsec policies introduced
1958 with the Linux 2.6.34 kernel. For details see the example scenarios
1959 ikev2/nat-two-rw-mark, ikev2/rw-nat-mark-in-out and ikev2/net2net-psk-dscp.
1961 - The PLUTO_MARK_IN and PLUTO_ESP_ENC environment variables can be used
1962 in a user-specific updown script to set marks on inbound ESP or
1965 - The openssl plugin now supports X.509 certificate and CRL functions.
1967 - OCSP/CRL checking in IKEv2 has been moved to the revocation plugin, enabled
1968 by default. Please update manual load directives in strongswan.conf.
1970 - RFC3779 ipAddrBlock constraint checking has been moved to the addrblock
1971 plugin, disabled by default. Enable it and update manual load directives
1972 in strongswan.conf, if required.
1974 - The pki utility supports CRL generation using the --signcrl command.
1976 - The ipsec pki --self, --issue and --req commands now support output in
1977 PEM format using the --outform pem option.
1979 - The major refactoring of the IKEv1 Mode Config functionality now allows
1980 the transport and handling of any Mode Config attribute.
1982 - The RADIUS proxy plugin eap-radius now supports multiple servers. Configured
1983 servers are chosen randomly, with the option to prefer a specific server.
1984 Non-responding servers are degraded by the selection process.
1986 - The ipsec pool tool manages arbitrary configuration attributes stored
1987 in an SQL database. ipsec pool --help gives the details.
1989 - The new eap-simaka-sql plugin acts as a backend for EAP-SIM and EAP-AKA,
1990 reading triplets/quintuplets from an SQL database.
1992 - The High Availability plugin now supports a HA enabled in-memory address
1993 pool and Node reintegration without IKE_SA rekeying. The latter allows
1994 clients without IKE_SA rekeying support to keep connected during
1995 reintegration. Additionally, many other issues have been fixed in the ha
1998 - Fixed a potential remote code execution vulnerability resulting from
1999 the misuse of snprintf(). The vulnerability is exploitable by
2000 unauthenticated users.
2006 - The IKEv2 High Availability plugin has been integrated. It provides
2007 load sharing and failover capabilities in a cluster of currently two nodes,
2008 based on an extend ClusterIP kernel module. More information is available at
2009 https://wiki.strongswan.org/projects/strongswan/wiki/HighAvailability.
2010 The development of the High Availability functionality was sponsored by
2011 secunet Security Networks AG.
2013 - Added IKEv1 and IKEv2 configuration support for the AES-GMAC
2014 authentication-only ESP cipher. Our aes_gmac kernel patch or a Linux
2015 2.6.34 kernel is required to make AES-GMAC available via the XFRM
2018 - Added support for Diffie-Hellman groups 22, 23 and 24 to the gmp, gcrypt
2019 and openssl plugins, usable by both pluto and charon. The new proposal
2020 keywords are modp1024s160, modp2048s224 and modp2048s256. Thanks to Joy Latten
2021 from IBM for his contribution.
2023 - The IKEv1 pluto daemon supports RAM-based virtual IP pools using
2024 the rightsourceip directive with a subnet from which addresses
2027 - The ipsec pki --gen and --pub commands now allow the output of
2028 private and public keys in PEM format using the --outform pem
2029 command line option.
2031 - The new DHCP plugin queries virtual IP addresses for clients from a DHCP
2032 server using broadcasts, or a defined server using the
2033 charon.plugins.dhcp.server strongswan.conf option. DNS/WINS server information
2034 is additionally served to clients if the DHCP server provides such
2035 information. The plugin is used in ipsec.conf configurations having
2036 rightsourceip set to %dhcp.
2038 - A new plugin called farp fakes ARP responses for virtual IP addresses
2039 handed out to clients from the IKEv2 daemon charon. The plugin lets a
2040 road-warrior act as a client on the local LAN if it uses a virtual IP
2041 from the responders subnet, e.g. acquired using the DHCP plugin.
2043 - The existing IKEv2 socket implementations have been migrated to the
2044 socket-default and the socket-raw plugins. The new socket-dynamic plugin
2045 binds sockets dynamically to ports configured via the left-/rightikeport
2046 ipsec.conf connection parameters.
2048 - The android charon plugin stores received DNS server information as "net.dns"
2049 system properties, as used by the Android platform.
2055 - The IKEv2 daemon supports RFC 3779 IP address block constraints
2056 carried as a critical X.509v3 extension in the peer certificate.
2058 - The ipsec pool --add|del dns|nbns command manages DNS and NBNS name
2059 server entries that are sent via the IKEv1 Mode Config or IKEv2
2060 Configuration Payload to remote clients.
2062 - The Camellia cipher can be used as an IKEv1 encryption algorithm.
2064 - The IKEv1 and IKEV2 daemons now check certificate path length constraints.
2066 - The new ipsec.conf conn option "inactivity" closes a CHILD_SA if no traffic
2067 was sent or received within the given interval. To close the complete IKE_SA
2068 if its only CHILD_SA was inactive, set the global strongswan.conf option
2069 "charon.inactivity_close_ike" to yes.
2071 - More detailed IKEv2 EAP payload information in debug output
2073 - IKEv2 EAP-SIM and EAP-AKA share joint libsimaka library
2075 - Added required userland changes for proper SHA256 and SHA384/512 in ESP that
2076 will be introduced with Linux 2.6.33. The "sha256"/"sha2_256" keyword now
2077 configures the kernel with 128 bit truncation, not the non-standard 96
2078 bit truncation used by previous releases. To use the old 96 bit truncation
2079 scheme, the new "sha256_96" proposal keyword has been introduced.
2081 - Fixed IPComp in tunnel mode, stripping out the duplicated outer header. This
2082 change makes IPcomp tunnel mode connections incompatible with previous
2083 releases; disable compression on such tunnels.
2085 - Fixed BEET mode connections on recent kernels by installing SAs with
2086 appropriate traffic selectors, based on a patch by Michael Rossberg.
2088 - Using extensions (such as BEET mode) and crypto algorithms (such as twofish,
2089 serpent, sha256_96) allocated in the private use space now require that we
2090 know its meaning, i.e. we are talking to strongSwan. Use the new
2091 "charon.send_vendor_id" option in strongswan.conf to let the remote peer know
2094 - Experimental support for draft-eronen-ipsec-ikev2-eap-auth, where the
2095 responder omits public key authentication in favor of a mutual authentication
2096 method. To enable EAP-only authentication, set rightauth=eap on the responder
2097 to rely only on the MSK constructed AUTH payload. This not-yet standardized
2098 extension requires the strongSwan vendor ID introduced above.
2100 - The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus
2101 allowing interoperability.
2107 - The IKEv1 pluto daemon can now use SQL-based address pools to deal out
2108 virtual IP addresses as a Mode Config server. The pool capability has been
2109 migrated from charon's sql plugin to a new attr-sql plugin which is loaded
2110 by libstrongswan and which can be used by both daemons either with a SQLite
2111 or MySQL database and the corresponding plugin.
2113 - Plugin names have been streamlined: EAP plugins now have a dash after eap
2114 (e.g. eap-sim), as it is used with the --enable-eap-sim ./configure option.
2115 Plugin configuration sections in strongswan.conf now use the same name as the
2116 plugin itself (i.e. with a dash). Make sure to update "load" directives and
2117 the affected plugin sections in existing strongswan.conf files.
2119 - The private/public key parsing and encoding has been split up into
2120 separate pkcs1, pgp, pem and dnskey plugins. The public key implementation
2121 plugins gmp, gcrypt and openssl can all make use of them.
2123 - The EAP-AKA plugin can use different backends for USIM/quintuplet
2124 calculations, very similar to the EAP-SIM plugin. The existing 3GPP2 software
2125 implementation has been migrated to a separate plugin.
2127 - The IKEv2 daemon charon gained basic PGP support. It can use locally installed
2128 peer certificates and can issue signatures based on RSA private keys.
2130 - The new 'ipsec pki' tool provides a set of commands to maintain a public
2131 key infrastructure. It currently supports operations to create RSA and ECDSA
2132 private/public keys, calculate fingerprints and issue or verify certificates.
2134 - Charon uses a monotonic time source for statistics and job queueing, behaving
2135 correctly if the system time changes (e.g. when using NTP).
2137 - In addition to time based rekeying, charon supports IPsec SA lifetimes based
2138 on processed volume or number of packets. They new ipsec.conf parameters
2139 'lifetime' (an alias to 'keylife'), 'lifebytes' and 'lifepackets' handle
2140 SA timeouts, while the parameters 'margintime' (an alias to rekeymargin),
2141 'marginbytes' and 'marginpackets' trigger the rekeying before a SA expires.
2142 The existing parameter 'rekeyfuzz' affects all margins.
2144 - If no CA/Gateway certificate is specified in the NetworkManager plugin,
2145 charon uses a set of trusted root certificates preinstalled by distributions.
2146 The directory containing CA certificates can be specified using the
2147 --with-nm-ca-dir=path configure option.
2149 - Fixed the encoding of the Email relative distinguished name in left|rightid
2152 - Fixed the broken parsing of PKCS#7 wrapped certificates by the pluto daemon.
2154 - Fixed smartcard-based authentication in the pluto daemon which was broken by
2155 the ECDSA support introduced with the 4.3.2 release.
2157 - A patch contributed by Heiko Hund fixes mixed IPv6 in IPv4 and vice versa
2158 tunnels established with the IKEv1 pluto daemon.
2160 - The pluto daemon now uses the libstrongswan x509 plugin for certificates and
2161 CRls and the struct id type was replaced by identification_t used by charon
2162 and the libstrongswan library.
2168 - IKEv2 charon daemon ported to FreeBSD and Mac OS X. Installation details can
2169 be found on wiki.strongswan.org.
2171 - ipsec statusall shows the number of bytes transmitted and received over
2172 ESP connections configured by the IKEv2 charon daemon.
2174 - The IKEv2 charon daemon supports include files in ipsec.secrets.
2180 - The configuration option --enable-integrity-test plus the strongswan.conf
2181 option libstrongswan.integrity_test = yes activate integrity tests
2182 of the IKE daemons charon and pluto, libstrongswan and all loaded
2183 plugins. Thus dynamic library misconfigurations and non-malicious file
2184 manipulations can be reliably detected.
2186 - The new default setting libstrongswan.ecp_x_coordinate_only=yes allows
2187 IKEv1 interoperability with MS Windows using the ECP DH groups 19 and 20.
2189 - The IKEv1 pluto daemon now supports the AES-CCM and AES-GCM ESP
2190 authenticated encryption algorithms.
2192 - The IKEv1 pluto daemon now supports V4 OpenPGP keys.
2194 - The RDN parser vulnerability discovered by Orange Labs research team
2195 was not completely fixed in version 4.3.2. Some more modifications
2196 had to be applied to the asn1_length() function to make it robust.
2202 - The new gcrypt plugin provides symmetric cipher, hasher, RNG, Diffie-Hellman
2203 and RSA crypto primitives using the LGPL licensed GNU gcrypt library.
2205 - libstrongswan features an integrated crypto selftest framework for registered
2206 algorithms. The test-vector plugin provides a first set of test vectors and
2207 allows pluto and charon to rely on tested crypto algorithms.
2209 - pluto can now use all libstrongswan plugins with the exception of x509 and xcbc.
2210 Thanks to the openssl plugin, the ECP Diffie-Hellman groups 19, 20, 21, 25, and
2211 26 as well as ECDSA-256, ECDSA-384, and ECDSA-521 authentication can be used
2214 - Applying their fuzzing tool, the Orange Labs vulnerability research team found
2215 another two DoS vulnerabilities, one in the rather old ASN.1 parser of Relative
2216 Distinguished Names (RDNs) and a second one in the conversion of ASN.1 UTCTIME
2217 and GENERALIZEDTIME strings to a time_t value.
2223 - The nm plugin now passes DNS/NBNS server information to NetworkManager,
2224 allowing a gateway administrator to set DNS/NBNS configuration on clients
2227 - The nm plugin also accepts CA certificates for gateway authentication. If
2228 a CA certificate is configured, strongSwan uses the entered gateway address
2229 as its identity, requiring the gateways certificate to contain the same as
2230 subjectAltName. This allows a gateway administrator to deploy the same
2231 certificates to Windows 7 and NetworkManager clients.
2233 - The command ipsec purgeike deletes IKEv2 SAs that don't have a CHILD SA.
2234 The command ipsec down <conn>{n} deletes CHILD SA instance n of connection
2235 <conn> whereas ipsec down <conn>{*} deletes all CHILD SA instances.
2236 The command ipsec down <conn>[n] deletes IKE SA instance n of connection
2237 <conn> plus dependent CHILD SAs whereas ipsec down <conn>[*] deletes all
2238 IKE SA instances of connection <conn>.
2240 - Fixed a regression introduced in 4.3.0 where EAP authentication calculated
2241 the AUTH payload incorrectly. Further, the EAP-MSCHAPv2 MSK key derivation
2242 has been updated to be compatible with the Windows 7 Release Candidate.
2244 - Refactored installation of triggering policies. Routed policies are handled
2245 outside of IKE_SAs to keep them installed in any case. A tunnel gets
2246 established only once, even if initiation is delayed due network outages.
2248 - Improved the handling of multiple acquire signals triggered by the kernel.
2250 - Fixed two DoS vulnerabilities in the charon daemon that were discovered by
2251 fuzzing techniques: 1) Sending a malformed IKE_SA_INIT request leaved an
2252 incomplete state which caused a null pointer dereference if a subsequent
2253 CREATE_CHILD_SA request was sent. 2) Sending an IKE_AUTH request with either
2254 a missing TSi or TSr payload caused a null pointer dereference because the
2255 checks for TSi and TSr were interchanged. The IKEv2 fuzzer used was
2256 developed by the Orange Labs vulnerability research team. The tool was
2257 initially written by Gabriel Campana and is now maintained by Laurent Butti.
2259 - Added support for AES counter mode in ESP in IKEv2 using the proposal
2260 keywords aes128ctr, aes192ctr and aes256ctr.
2262 - Further progress in refactoring pluto: Use of the curl and ldap plugins
2263 for fetching crls and OCSP. Use of the random plugin to get keying material
2264 from /dev/random or /dev/urandom. Use of the openssl plugin as an alternative
2265 to the aes, des, sha1, sha2, and md5 plugins. The blowfish, twofish, and
2266 serpent encryption plugins are now optional and are not enabled by default.
2272 - Support for the IKEv2 Multiple Authentication Exchanges extension (RFC4739).
2273 Initiators and responders can use several authentication rounds (e.g. RSA
2274 followed by EAP) to authenticate. The new ipsec.conf leftauth/rightauth and
2275 leftauth2/rightauth2 parameters define own authentication rounds or setup
2276 constraints for the remote peer. See the ipsec.conf man page for more details.
2278 - If glibc printf hooks (register_printf_function) are not available,
2279 strongSwan can use the vstr string library to run on non-glibc systems.
2281 - The IKEv2 charon daemon can now configure the ESP CAMELLIA-CBC cipher
2282 (esp=camellia128|192|256).
2284 - Refactored the pluto and scepclient code to use basic functions (memory
2285 allocation, leak detective, chunk handling, printf_hooks, strongswan.conf
2286 attributes, ASN.1 parser, etc.) from the libstrongswan library.
2288 - Up to two DNS and WINS servers to be sent via IKEv1 ModeConfig can be
2289 configured in the pluto section of strongswan.conf.
2295 - The new server-side EAP RADIUS plugin (--enable-eap-radius)
2296 relays EAP messages to and from a RADIUS server. Successfully
2297 tested with with a freeradius server using EAP-MD5 and EAP-SIM.
2299 - A vulnerability in the Dead Peer Detection (RFC 3706) code was found by
2300 Gerd v. Egidy <gerd.von.egidy@intra2net.com> of Intra2net AG affecting
2301 all Openswan and strongSwan releases. A malicious (or expired ISAKMP)
2302 R_U_THERE or R_U_THERE_ACK Dead Peer Detection packet can cause the
2303 pluto IKE daemon to crash and restart. No authentication or encryption
2304 is required to trigger this bug. One spoofed UDP packet can cause the
2305 pluto IKE daemon to restart and be unresponsive for a few seconds while
2306 restarting. This DPD null state vulnerability has been officially
2307 registered as CVE-2009-0790 and is fixed by this release.
2309 - ASN.1 to time_t conversion caused a time wrap-around for
2310 dates after Jan 18 03:14:07 UTC 2038 on 32-bit platforms.
2311 As a workaround such dates are set to the maximum representable
2312 time, i.e. Jan 19 03:14:07 UTC 2038.
2314 - Distinguished Names containing wildcards (*) are not sent in the
2315 IDr payload anymore.
2321 - Fixed a use-after-free bug in the DPD timeout section of the
2322 IKEv1 pluto daemon which sporadically caused a segfault.
2324 - Fixed a crash in the IKEv2 charon daemon occurring with
2325 mixed RAM-based and SQL-based virtual IP address pools.
2327 - Fixed ASN.1 parsing of algorithmIdentifier objects where the
2328 parameters field is optional.
2330 - Ported nm plugin to NetworkManager 7.1.
2336 - Support of the EAP-MSCHAPv2 protocol enabled by the option
2337 --enable-eap-mschapv2. Requires the MD4 hash algorithm enabled
2338 either by --enable-md4 or --enable-openssl.
2340 - Assignment of up to two DNS and up to two WINS servers to peers via
2341 the IKEv2 Configuration Payload (CP). The IPv4 or IPv6 nameserver
2342 addresses are defined in strongswan.conf.
2344 - The strongSwan applet for the Gnome NetworkManager is now built and
2345 distributed as a separate tarball under the name NetworkManager-strongswan.
2351 - Fixed ESP NULL encryption broken by the refactoring of keymat.c.
2352 Also introduced proper initialization and disposal of keying material.
2354 - Fixed the missing listing of connection definitions in ipsec statusall
2355 broken by an unfortunate local variable overload.
2361 - Several performance improvements to handle thousands of tunnels with almost
2362 linear upscaling. All relevant data structures have been replaced by faster
2363 counterparts with better lookup times.
2365 - Better parallelization to run charon on multiple cores. Due to improved
2366 resource locking and other optimizations the daemon can take full
2367 advantage of 16 or even more cores.
2369 - The load-tester plugin can use a NULL Diffie-Hellman group and simulate
2370 unique identities and certificates by signing peer certificates using a CA
2373 - The redesigned stroke in-memory IP pool handles leases. The "ipsec leases"
2374 command queries assigned leases.
2376 - Added support for smartcards in charon by using the ENGINE API provided by
2377 OpenSSL, based on patches by Michael Roßberg.
2379 - The Padlock plugin supports the hardware RNG found on VIA CPUs to provide a
2380 reliable source of randomness.
2385 - Flexible configuration of logging subsystem allowing to log to multiple
2386 syslog facilities or to files using fine-grained log levels for each target.
2388 - Load testing plugin to do stress testing of the IKEv2 daemon against self
2389 or another host. Found and fixed issues during tests in the multi-threaded
2390 use of the OpenSSL plugin.
2392 - Added profiling code to synchronization primitives to find bottlenecks if
2393 running on multiple cores. Found and fixed an issue where parts of the
2394 Diffie-Hellman calculation acquired an exclusive lock. This greatly improves
2395 parallelization to multiple cores.
2397 - updown script invocation has been separated into a plugin of its own to
2398 further slim down the daemon core.
2400 - Separated IKE_SA/CHILD_SA key derivation process into a closed system,
2401 allowing future implementations to use a secured environment in e.g. kernel
2404 - The kernel interface of charon has been modularized. XFRM NETLINK (default)
2405 and PFKEY (--enable-kernel-pfkey) interface plugins for the native IPsec
2406 stack of the Linux 2.6 kernel as well as a PFKEY interface for the KLIPS
2407 IPsec stack (--enable-kernel-klips) are provided.
2409 - Basic Mobile IPv6 support has been introduced, securing Binding Update
2410 messages as well as tunneled traffic between Mobile Node and Home Agent.
2411 The installpolicy=no option allows peaceful cooperation with a dominant
2412 mip6d daemon and the new type=transport_proxy implements the special MIPv6
2413 IPsec transport proxy mode where the IKEv2 daemon uses the Care-of-Address
2414 but the IPsec SA is set up for the Home Address.
2416 - Implemented migration of Mobile IPv6 connections using the KMADDRESS
2417 field contained in XFRM_MSG_MIGRATE messages sent by the mip6d daemon
2418 via the Linux 2.6.28 (or appropriately patched) kernel.
2424 - IKEv2 charon daemon supports authentication based on raw public keys
2425 stored in the SQL database backend. The ipsec listpubkeys command
2426 lists the available raw public keys via the stroke interface.
2428 - Several MOBIKE improvements: Detect changes in NAT mappings in DPD exchanges,
2429 handle events if kernel detects NAT mapping changes in UDP-encapsulated
2430 ESP packets (requires kernel patch), reuse old addresses in MOBIKE updates as
2431 long as possible and other fixes.
2433 - Fixed a bug in addr_in_subnet() which caused insertion of wrong source
2434 routes for destination subnets having netwmasks not being a multiple of 8 bits.
2435 Thanks go to Wolfgang Steudel, TU Ilmenau for reporting this bug.
2441 - Fixed a Denial-of-Service vulnerability where an IKE_SA_INIT message with
2442 a KE payload containing zeroes only can cause a crash of the IKEv2 charon
2443 daemon due to a NULL pointer returned by the mpz_export() function of the
2444 GNU Multiprecision Library (GMP). Thanks go to Mu Dynamics Research Labs
2445 for making us aware of this problem.
2447 - The new agent plugin provides a private key implementation on top of an
2450 - The NetworkManager plugin has been extended to support certificate client
2451 authentication using RSA keys loaded from a file or using ssh-agent.
2453 - Daemon capability dropping has been ported to libcap and must be enabled
2454 explicitly --with-capabilities=libcap. Future version will support the
2455 newer libcap2 library.
2457 - ipsec listalgs lists the IKEv2 cryptografic algorithms registered with the
2458 charon keying daemon.
2464 - A NetworkManager plugin allows GUI-based configuration of road-warrior
2465 clients in a simple way. It features X509 based gateway authentication
2466 and EAP client authentication, tunnel setup/teardown and storing passwords
2467 in the Gnome Keyring.
2469 - A new EAP-GTC plugin implements draft-sheffer-ikev2-gtc-00.txt and allows
2470 username/password authentication against any PAM service on the gateway.
2471 The new EAP method interacts nicely with the NetworkManager plugin and allows
2472 client authentication against e.g. LDAP.
2474 - Improved support for the EAP-Identity method. The new ipsec.conf eap_identity
2475 parameter defines an additional identity to pass to the server in EAP
2478 - The "ipsec statusall" command now lists CA restrictions, EAP
2479 authentication types and EAP identities.
2481 - Fixed two multithreading deadlocks occurring when starting up
2482 several hundred tunnels concurrently.
2484 - Fixed the --enable-integrity-test configure option which
2485 computes a SHA-1 checksum over the libstrongswan library.
2491 - Consistent logging of IKE and CHILD SAs at the audit (AUD) level.
2493 - Improved the performance of the SQL-based virtual IP address pool
2494 by introducing an additional addresses table. The leases table
2495 storing only history information has become optional and can be
2496 disabled by setting charon.plugins.sql.lease_history = no in
2499 - The XFRM_STATE_AF_UNSPEC flag added to xfrm.h allows IPv4-over-IPv6
2500 and IPv6-over-IPv4 tunnels with the 2.6.26 and later Linux kernels.
2502 - management of different virtual IP pools for different
2503 network interfaces have become possible.
2505 - fixed a bug which prevented the assignment of more than 256
2506 virtual IP addresses from a pool managed by an sql database.
2508 - fixed a bug which did not delete own IPCOMP SAs in the kernel.
2514 - Added statistics functions to ipsec pool --status and ipsec pool --leases
2515 and input validation checks to various ipsec pool commands.
2517 - ipsec statusall now lists all loaded charon plugins and displays
2518 the negotiated IKEv2 cipher suite proposals.
2520 - The openssl plugin supports the elliptic curve Diffie-Hellman groups
2521 19, 20, 21, 25, and 26.
2523 - The openssl plugin supports ECDSA authentication using elliptic curve
2526 - Fixed a bug in stroke which caused multiple charon threads to close
2527 the file descriptors during packet transfers over the stroke socket.
2529 - ESP sequence numbers are now migrated in IPsec SA updates handled by
2530 MOBIKE. Works only with Linux kernels >= 2.6.17.
2536 - Fixed the strongswan.conf path configuration problem that occurred when
2537 --sysconfig was not set explicitly in ./configure.
2539 - Fixed a number of minor bugs that where discovered during the 4th
2540 IKEv2 interoperability workshop in San Antonio, TX.
2546 - Plugins for libstrongswan and charon can optionally be loaded according
2547 to a configuration in strongswan.conf. Most components provide a
2548 "load = " option followed by a space separated list of plugins to load.
2549 This allows e.g. the fallback from a hardware crypto accelerator to
2550 to software-based crypto plugins.
2552 - Charons SQL plugin has been extended by a virtual IP address pool.
2553 Configurations with a rightsourceip=%poolname setting query a SQLite or
2554 MySQL database for leases. The "ipsec pool" command helps in administrating
2555 the pool database. See ipsec pool --help for the available options
2557 - The Authenticated Encryption Algorithms AES-CCM-8/12/16 and AES-GCM-8/12/16
2558 for ESP are now supported starting with the Linux 2.6.25 kernel. The
2559 syntax is e.g. esp=aes128ccm12 or esp=aes256gcm16.
2565 - Support for "Hash and URL" encoded certificate payloads has been implemented
2566 in the IKEv2 daemon charon. Using the "certuribase" option of a CA section
2567 allows to assign a base URL to all certificates issued by the specified CA.
2568 The final URL is then built by concatenating that base and the hex encoded
2569 SHA1 hash of the DER encoded certificate. Note that this feature is disabled
2570 by default and must be enabled using the option "charon.hash_and_url".
2572 - The IKEv2 daemon charon now supports the "uniqueids" option to close multiple
2573 IKE_SAs with the same peer. The option value "keep" prefers existing
2574 connection setups over new ones, where the value "replace" replaces existing
2577 - The crypto factory in libstrongswan additionally supports random number
2578 generators, plugins may provide other sources of randomness. The default
2579 plugin reads raw random data from /dev/(u)random.
2581 - Extended the credential framework by a caching option to allow plugins
2582 persistent caching of fetched credentials. The "cachecrl" option has been
2585 - The new trustchain verification introduced in 4.2.0 has been parallelized.
2586 Threads fetching CRL or OCSP information no longer block other threads.
2588 - A new IKEv2 configuration attribute framework has been introduced allowing
2589 plugins to provide virtual IP addresses, and in the future, other
2590 configuration attribute services (e.g. DNS/WINS servers).
2592 - The stroke plugin has been extended to provide virtual IP addresses from
2593 a pool defined in ipsec.conf. The "rightsourceip" parameter now accepts
2594 address pools in CIDR notation (e.g. 10.1.1.0/24). The parameter also accepts
2595 the value "%poolname", where "poolname" identifies a pool provided by a
2598 - Fixed compilation on uClibc and a couple of other minor bugs.
2600 - Set DPD defaults in ipsec starter to dpd_delay=30s and dpd_timeout=150s.
2602 - The IKEv1 pluto daemon now supports the ESP encryption algorithm CAMELLIA
2603 with key lengths of 128, 192, and 256 bits, as well as the authentication
2604 algorithm AES_XCBC_MAC. Configuration example: esp=camellia192-aesxcbc.
2610 - libstrongswan has been modularized to attach crypto algorithms,
2611 credential implementations (keys, certificates) and fetchers dynamically
2612 through plugins. Existing code has been ported to plugins:
2613 - RSA/Diffie-Hellman implementation using the GNU Multi Precision library
2614 - X509 certificate system supporting CRLs, OCSP and attribute certificates
2615 - Multiple plugins providing crypto algorithms in software
2616 - CURL and OpenLDAP fetcher
2618 - libstrongswan gained a relational database API which uses pluggable database
2619 providers. Plugins for MySQL and SQLite are available.
2621 - The IKEv2 keying daemon charon is more extensible. Generic plugins may provide
2622 connection configuration, credentials and EAP methods or control the daemon.
2623 Existing code has been ported to plugins:
2624 - EAP-AKA, EAP-SIM, EAP-MD5 and EAP-Identity
2625 - stroke configuration, credential and control (compatible to pluto)
2626 - XML bases management protocol to control and query the daemon
2627 The following new plugins are available:
2628 - An experimental SQL configuration, credential and logging plugin on
2629 top of either MySQL or SQLite
2630 - A unit testing plugin to run tests at daemon startup
2632 - The authentication and credential framework in charon has been heavily
2633 refactored to support modular credential providers, proper
2634 CERTREQ/CERT payload exchanges and extensible authorization rules.
2636 - The framework of strongSwan Manager has evolved to the web application
2637 framework libfast (FastCGI Application Server w/ Templates) and is usable
2638 by other applications.
2644 - IKE rekeying in NAT situations did not inherit the NAT conditions
2645 to the rekeyed IKE_SA so that the UDP encapsulation was lost with
2646 the next CHILD_SA rekeying.
2648 - Wrong type definition of the next_payload variable in id_payload.c
2649 caused an INVALID_SYNTAX error on PowerPC platforms.
2651 - Implemented IKEv2 EAP-SIM server and client test modules that use
2652 triplets stored in a file. For details on the configuration see
2653 the scenario 'ikev2/rw-eap-sim-rsa'.
2659 - Fixed error in the ordering of the certinfo_t records in the ocsp cache that
2660 caused multiple entries of the same serial number to be created.
2662 - Implementation of a simple EAP-MD5 module which provides CHAP
2663 authentication. This may be interesting in conjunction with certificate
2664 based server authentication, as weak passwords can't be brute forced
2665 (in contradiction to traditional IKEv2 PSK).
2667 - A complete software based implementation of EAP-AKA, using algorithms
2668 specified in 3GPP2 (S.S0055). This implementation does not use an USIM,
2669 but reads the secrets from ipsec.secrets. Make sure to read eap_aka.h
2672 - Support for vendor specific EAP methods using Expanded EAP types. The
2673 interface to EAP modules has been slightly changed, so make sure to
2674 check the changes if you're already rolling your own modules.
2680 - The default _updown script now dynamically inserts and removes ip6tables
2681 firewall rules if leftfirewall=yes is set in IPv6 connections. New IPv6
2682 net-net and roadwarrior (PSK/RSA) scenarios for both IKEv1 and IKEV2 were
2685 - Implemented RFC4478 repeated authentication to force EAP/Virtual-IP clients
2686 to reestablish an IKE_SA within a given timeframe.
2688 - strongSwan Manager supports configuration listing, initiation and termination
2689 of IKE and CHILD_SAs.
2691 - Fixes and improvements to multithreading code.
2693 - IKEv2 plugins have been renamed to libcharon-* to avoid naming conflicts.
2694 Make sure to remove the old plugins in $libexecdir/ipsec, otherwise they get
2701 - Removed recursive pthread mutexes since uClibc doesn't support them.
2707 - In NAT traversal situations and multiple queued Quick Modes,
2708 those pending connections inserted by auto=start after the
2709 port floating from 500 to 4500 were erroneously deleted.
2711 - Added a "forceencaps" connection parameter to enforce UDP encapsulation
2712 to surmount restrictive firewalls. NAT detection payloads are faked to
2713 simulate a NAT situation and trick the other peer into NAT mode (IKEv2 only).
2715 - Preview of strongSwan Manager, a web based configuration and monitoring
2716 application. It uses a new XML control interface to query the IKEv2 daemon
2717 (see https://wiki.strongswan.org/wiki/Manager).
2719 - Experimental SQLite configuration backend which will provide the configuration
2720 interface for strongSwan Manager in future releases.
2722 - Further improvements to MOBIKE support.
2728 - Since some third party IKEv2 implementations run into
2729 problems with strongSwan announcing MOBIKE capability per
2730 default, MOBIKE can be disabled on a per-connection-basis
2731 using the mobike=no option. Whereas mobike=no disables the
2732 sending of the MOBIKE_SUPPORTED notification and the floating
2733 to UDP port 4500 with the IKE_AUTH request even if no NAT
2734 situation has been detected, strongSwan will still support
2735 MOBIKE acting as a responder.
2737 - the default ipsec routing table plus its corresponding priority
2738 used for inserting source routes has been changed from 100 to 220.
2739 It can be configured using the --with-ipsec-routing-table and
2740 --with-ipsec-routing-table-prio options.
2742 - the --enable-integrity-test configure option tests the
2743 integrity of the libstrongswan crypto code during the charon
2746 - the --disable-xauth-vid configure option disables the sending
2747 of the XAUTH vendor ID. This can be used as a workaround when
2748 interoperating with some Windows VPN clients that get into
2749 trouble upon reception of an XAUTH VID without eXtended
2750 AUTHentication having been configured.
2752 - ipsec stroke now supports the rereadsecrets, rereadaacerts,
2753 rereadacerts, and listacerts options.
2759 - If a DNS lookup failure occurs when resolving right=%<FQDN>
2760 or right=<FQDN> combined with rightallowany=yes then the
2761 connection is not updated by ipsec starter thus preventing
2762 the disruption of an active IPsec connection. Only if the DNS
2763 lookup successfully returns with a changed IP address the
2764 corresponding connection definition is updated.
2766 - Routes installed by the keying daemons are now in a separate
2767 routing table with the ID 100 to avoid conflicts with the main
2768 table. Route lookup for IKEv2 traffic is done in userspace to ignore
2769 routes installed for IPsec, as IKE traffic shouldn't get encapsulated.
2775 - The pluto IKEv1 daemon now exhibits the same behavior as its
2776 IKEv2 companion charon by inserting an explicit route via the
2777 _updown script only if a sourceip exists. This is admissible
2778 since routing through the IPsec tunnel is handled automatically
2779 by NETKEY's IPsec policies. As a consequence the left|rightnexthop
2780 parameter is not required any more.
2782 - The new IKEv1 parameter right|leftallowany parameters helps to handle
2783 the case where both peers possess dynamic IP addresses that are
2784 usually resolved using DynDNS or a similar service. The configuration
2789 can be used by the initiator to start up a connection to a peer
2790 by resolving peer.foo.bar into the currently allocated IP address.
2791 Thanks to the rightallowany flag the connection behaves later on
2796 so that the peer can rekey the connection as an initiator when his
2797 IP address changes. An alternative notation is
2801 which will implicitly set rightallowany=yes.
2803 - ipsec starter now fails more gracefully in the presence of parsing
2804 errors. Flawed ca and conn section are discarded and pluto is started
2805 if non-fatal errors only were encountered. If right=%peer.foo.bar
2806 cannot be resolved by DNS then right=%any will be used so that passive
2807 connections as a responder are still possible.
2809 - The new pkcs11initargs parameter that can be placed in the
2810 setup config section of /etc/ipsec.conf allows the definition
2811 of an argument string that is used with the PKCS#11 C_Initialize()
2812 function. This non-standard feature is required by the NSS softoken
2813 library. This patch was contributed by Robert Varga.
2815 - Fixed a bug in ipsec starter introduced by strongswan-2.8.5
2816 which caused a segmentation fault in the presence of unknown
2817 or misspelt keywords in ipsec.conf. This bug fix was contributed
2820 - Partial support for MOBIKE in IKEv2. The initiator acts on interface/
2821 address configuration changes and updates IKE and IPsec SAs dynamically.
2827 - IKEv2 peer configuration selection now can be based on a given
2828 certification authority using the rightca= statement.
2830 - IKEv2 authentication based on RSA signatures now can handle multiple
2831 certificates issued for a given peer ID. This allows a smooth transition
2832 in the case of a peer certificate renewal.
2834 - IKEv2: Support for requesting a specific virtual IP using leftsourceip on the
2835 client and returning requested virtual IPs using rightsourceip=%config
2836 on the server. If the server does not support configuration payloads, the
2837 client enforces its leftsourceip parameter.
2839 - The ./configure options --with-uid/--with-gid allow pluto and charon
2840 to drop their privileges to a minimum and change to an other UID/GID. This
2841 improves the systems security, as a possible intruder may only get the
2842 CAP_NET_ADMIN capability.
2844 - Further modularization of charon: Pluggable control interface and
2845 configuration backend modules provide extensibility. The control interface
2846 for stroke is included, and further interfaces using DBUS (NetworkManager)
2847 or XML are on the way. A backend for storing configurations in the daemon
2848 is provided and more advanced backends (using e.g. a database) are trivial
2851 - Fixed a compilation failure in libfreeswan occurring with Linux kernel
2858 - Support for an additional Diffie-Hellman exchange when creating/rekeying
2859 a CHILD_SA in IKEv2 (PFS). PFS is enabled when the proposal contains a
2860 DH group (e.g. "esp=aes128-sha1-modp1536"). Further, DH group negotiation
2861 is implemented properly for rekeying.
2863 - Support for the AES-XCBC-96 MAC algorithm for IPsec SAs when using IKEv2
2864 (requires linux >= 2.6.20). It is enabled using e.g. "esp=aes256-aesxcbc".
2866 - Working IPv4-in-IPv6 and IPv6-in-IPv4 tunnels for linux >= 2.6.21.
2868 - Added support for EAP modules which do not establish an MSK.
2870 - Removed the dependencies from the /usr/include/linux/ headers by
2871 including xfrm.h, ipsec.h, and pfkeyv2.h in the distribution.
2873 - crlNumber is now listed by ipsec listcrls
2875 - The xauth_modules.verify_secret() function now passes the
2882 - Server side cookie support. If to may IKE_SAs are in CONNECTING state,
2883 cookies are enabled and protect against DoS attacks with faked source
2884 addresses. Number of IKE_SAs in CONNECTING state is also limited per
2885 peer address to avoid resource exhaustion. IKE_SA_INIT messages are
2886 compared to properly detect retransmissions and incoming retransmits are
2887 detected even if the IKE_SA is blocked (e.g. doing OCSP fetches).
2889 - The IKEv2 daemon charon now supports dynamic http- and ldap-based CRL
2890 fetching enabled by crlcheckinterval > 0 and caching fetched CRLs
2891 enabled by cachecrls=yes.
2893 - Added the configuration options --enable-nat-transport which enables
2894 the potentially insecure NAT traversal for IPsec transport mode and
2895 --disable-vendor-id which disables the sending of the strongSwan
2898 - Fixed a long-standing bug in the pluto IKEv1 daemon which caused
2899 a segmentation fault if a malformed payload was detected in the
2900 IKE MR2 message and pluto tried to send an encrypted notification
2903 - Added the NATT_IETF_02_N Vendor ID in order to support IKEv1 connections
2904 with Windows 2003 Server which uses a wrong VID hash.
2910 - Support of SHA2_384 hash function for protecting IKEv1
2911 negotiations and support of SHA2 signatures in X.509 certificates.
2913 - Fixed a serious bug in the computation of the SHA2-512 HMAC
2914 function. Introduced automatic self-test of all IKEv1 hash
2915 and hmac functions during pluto startup. Failure of a self-test
2916 currently issues a warning only but does not exit pluto [yet].
2918 - Support for SHA2-256/384/512 PRF and HMAC functions in IKEv2.
2920 - Full support of CA information sections. ipsec listcainfos
2921 now shows all collected crlDistributionPoints and OCSP
2924 - Support of the Online Certificate Status Protocol (OCSP) for IKEv2.
2925 This feature requires the HTTP fetching capabilities of the libcurl
2926 library which must be enabled by setting the --enable-http configure
2929 - Refactored core of the IKEv2 message processing code, allowing better
2930 code reuse and separation.
2932 - Virtual IP support in IKEv2 using INTERNAL_IP4/6_ADDRESS configuration
2933 payload. Additionally, the INTERNAL_IP4/6_DNS attribute is interpreted
2934 by the requestor and installed in a resolv.conf file.
2936 - The IKEv2 daemon charon installs a route for each IPsec policy to use
2937 the correct source address even if an application does not explicitly
2940 - Integrated the EAP framework into charon which loads pluggable EAP library
2941 modules. The ipsec.conf parameter authby=eap initiates EAP authentication
2942 on the client side, while the "eap" parameter on the server side defines
2943 the EAP method to use for client authentication.
2944 A generic client side EAP-Identity module and an EAP-SIM authentication
2945 module using a third party card reader implementation are included.
2947 - Added client side support for cookies.
2949 - Integrated the fixes done at the IKEv2 interoperability bakeoff, including
2950 strict payload order, correct INVALID_KE_PAYLOAD rejection and other minor
2951 fixes to enhance interoperability with other implementations.
2957 - strongSwan now interoperates with the NCP Secure Entry Client,
2958 the Shrew Soft VPN Client, and the Cisco VPN client, doing both
2959 XAUTH and Mode Config.
2961 - UNITY attributes are now recognized and UNITY_BANNER is set
2962 to a default string.
2968 - IKEv1: Support for extended authentication (XAUTH) in combination
2969 with ISAKMP Main Mode RSA or PSK authentication. Both client and
2970 server side were implemented. Handling of user credentials can
2971 be done by a run-time loadable XAUTH module. By default user
2972 credentials are stored in ipsec.secrets.
2974 - IKEv2: Support for reauthentication when rekeying
2976 - IKEv2: Support for transport mode
2978 - fixed a lot of bugs related to byte order
2980 - various other bugfixes
2986 - IKEv1: Implementation of ModeConfig push mode via the new connection
2987 keyword modeconfig=push allows interoperability with Cisco VPN gateways.
2989 - IKEv1: The command ipsec statusall now shows "DPD active" for all
2990 ISAKMP SAs that are under active Dead Peer Detection control.
2992 - IKEv2: Charon's logging and debugging framework has been completely rewritten.
2993 Instead of logger, special printf() functions are used to directly
2994 print objects like hosts (%H) identifications (%D), certificates (%Q),
2995 etc. The number of debugging levels have been reduced to:
2997 0 (audit), 1 (control), 2 (controlmore), 3 (raw), 4 (private)
2999 The debugging levels can either be specified statically in ipsec.conf as
3002 charondebug="lib 1, cfg 3, net 2"
3004 or changed at runtime via stroke as
3006 ipsec stroke loglevel cfg 2
3012 - Implemented full support for IPv6-in-IPv6 tunnels.
3014 - Added configuration options for dead peer detection in IKEv2. dpd_action
3015 types "clear", "hold" and "restart" are supported. The dpd_timeout
3016 value is not used, as the normal retransmission policy applies to
3017 detect dead peers. The dpd_delay parameter enables sending of empty
3018 informational message to detect dead peers in case of inactivity.
3020 - Added support for preshared keys in IKEv2. PSK keys configured in
3021 ipsec.secrets are loaded. The authby parameter specifies the authentication
3022 method to authenticate ourself, the other peer may use PSK or RSA.
3024 - Changed retransmission policy to respect the keyingtries parameter.
3026 - Added private key decryption. PEM keys encrypted with AES-128/192/256
3027 or 3DES are supported.
3029 - Implemented DES/3DES algorithms in libstrongswan. 3DES can be used to
3030 encrypt IKE traffic.
3032 - Implemented SHA-256/384/512 in libstrongswan, allows usage of certificates
3033 signed with such a hash algorithm.
3035 - Added initial support for updown scripts. The actions up-host/client and
3036 down-host/client are executed. The leftfirewall=yes parameter
3037 uses the default updown script to insert dynamic firewall rules, a custom
3038 updown script may be specified with the leftupdown parameter.
3044 - Added support for the auto=route ipsec.conf parameter and the
3045 ipsec route/unroute commands for IKEv2. This allows to set up IKE_SAs and
3046 CHILD_SAs dynamically on demand when traffic is detected by the
3049 - Added support for rekeying IKE_SAs in IKEv2 using the ikelifetime parameter.
3050 As specified in IKEv2, no reauthentication is done (unlike in IKEv1), only
3051 new keys are generated using perfect forward secrecy. An optional flag
3052 which enforces reauthentication will be implemented later.
3054 - "sha" and "sha1" are now treated as synonyms in the ike= and esp=
3055 algorithm configuration statements.
3061 - Full X.509 certificate trust chain verification has been implemented.
3062 End entity certificates can be exchanged via CERT payloads. The current
3063 default is leftsendcert=always, since CERTREQ payloads are not supported
3064 yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls.
3066 - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2
3067 would offer more possibilities for traffic selection, but the Linux kernel
3068 currently does not support it. That's why we stick with these simple
3069 ipsec.conf rules for now.
3071 - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no
3072 IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear,
3075 - Initial NAT traversal support in IKEv2. Charon includes NAT detection
3076 notify payloads to detect NAT routers between the peers. It switches
3077 to port 4500, uses UDP encapsulated ESP packets, handles peer address
3078 changes gracefully and sends keep alive message periodically.
3080 - Reimplemented IKE_SA state machine for charon, which allows simultaneous
3081 rekeying, more shared code, cleaner design, proper retransmission
3082 and a more extensible code base.
3084 - The mixed PSK/RSA roadwarrior detection capability introduced by the
3085 strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal
3086 payloads by the responder right before any defined IKE Main Mode state had
3087 been established. Although any form of bad proposal syntax was being correctly
3088 detected by the payload parser, the subsequent error handler didn't check
3089 the state pointer before logging current state information, causing an
3090 immediate crash of the pluto keying daemon due to a NULL pointer.
3096 - Added algorithm selection to charon: New default algorithms for
3097 ike=aes128-sha-modp2048, as both daemons support it. The default
3098 for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles
3099 the ike/esp parameter the same way as pluto. As this syntax does
3100 not allow specification of a pseudo random function, the same
3101 algorithm as for integrity is used (currently sha/md5). Supported
3103 Encryption: aes128, aes192, aes256
3104 Integrity/PRF: md5, sha (using hmac)
3105 DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192
3107 Encryption: aes128, aes192, aes256, 3des, blowfish128,
3108 blowfish192, blowfish256
3109 Integrity: md5, sha1
3110 More IKE encryption algorithms will come after porting libcrypto into
3113 - initial support for rekeying CHILD_SAs using IKEv2. Currently no
3114 perfect forward secrecy is used. The rekeying parameters rekey,
3115 rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported
3116 when using IKEv2. WARNING: charon currently is unable to handle
3117 simultaneous rekeying. To avoid such a situation, use a large
3118 rekeyfuzz, or even better, set rekey=no on one peer.
3120 - support for host2host, net2net, host2net (roadwarrior) tunnels
3121 using predefined RSA certificates (see uml scenarios for
3122 configuration examples).
3124 - new build environment featuring autotools. Features such
3125 as HTTP, LDAP and smartcard support may be enabled using
3126 the ./configure script. Changing install directories
3127 is possible, too. See ./configure --help for more details.
3129 - better integration of charon with ipsec starter, which allows
3130 (almost) transparent operation with both daemons. charon
3131 handles ipsec commands up, down, status, statusall, listall,
3132 listcerts and allows proper load, reload and delete of connections
3139 - initial support of the IKEv2 protocol. Connections in
3140 ipsec.conf designated by keyexchange=ikev2 are negotiated
3141 by the new IKEv2 charon keying daemon whereas those marked
3142 by keyexchange=ikev1 or the default keyexchange=ike are
3143 handled thy the IKEv1 pluto keying daemon. Currently only
3144 a limited subset of functions are available with IKEv2
3145 (Default AES encryption, authentication based on locally
3146 imported X.509 certificates, unencrypted private RSA keys
3147 in PKCS#1 file format, limited functionality of the ipsec
3154 - the dynamic iptables rules from the _updown_x509 template
3155 for KLIPS and the _updown_policy template for NETKEY have
3156 been merged into the default _updown script. The existing
3157 left|rightfirewall keyword causes the automatic insertion
3158 and deletion of ACCEPT rules for tunneled traffic upon
3159 the successful setup and teardown of an IPsec SA, respectively.
3160 left|rightfirewall can be used with KLIPS under any Linux 2.4
3161 kernel or with NETKEY under a Linux kernel version >= 2.6.16
3162 in conjunction with iptables >= 1.3.5. For NETKEY under a Linux
3163 kernel version < 2.6.16 which does not support IPsec policy
3164 matching yet, please continue to use a copy of the _updown_espmark
3165 template loaded via the left|rightupdown keyword.
3167 - a new left|righthostaccess keyword has been introduced which
3168 can be used in conjunction with left|rightfirewall and the
3169 default _updown script. By default leftfirewall=yes inserts
3170 a bi-directional iptables FORWARD rule for a local client network
3171 with a netmask different from 255.255.255.255 (single host).
3172 This does not allow to access the VPN gateway host via its
3173 internal network interface which is part of the client subnet
3174 because an iptables INPUT and OUTPUT rule would be required.
3175 lefthostaccess=yes will cause this additional ACCEPT rules to
3178 - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal
3179 payload is preparsed in order to find out whether the roadwarrior
3180 requests PSK or RSA so that a matching connection candidate can
3187 - the new _updown_policy template allows ipsec policy based
3188 iptables firewall rules. Required are iptables version
3189 >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes
3190 the _updown_espmark template, so that no INPUT mangle rules
3191 are required any more.
3193 - added support of DPD restart mode
3195 - ipsec starter now allows the use of wildcards in include
3196 statements as e.g. in "include /etc/my_ipsec/*.conf".
3197 Patch courtesy of Matthias Haas.
3199 - the Netscape OID 'employeeNumber' is now recognized and can be
3200 used as a Relative Distinguished Name in certificates.
3206 - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec
3207 command and not of ipsec setup any more.
3209 - ipsec starter now supports AH authentication in conjunction with
3210 ESP encryption. AH authentication is configured in ipsec.conf
3211 via the auth=ah parameter.
3213 - The command ipsec scencrypt|scdecrypt <args> is now an alias for
3214 ipsec whack --scencrypt|scdecrypt <args>.
3216 - get_sa_info() now determines for the native netkey IPsec stack
3217 the exact time of the last use of an active eroute. This information
3218 is used by the Dead Peer Detection algorithm and is also displayed by
3219 the ipsec status command.
3225 - running under the native Linux 2.6 IPsec stack, the function
3226 get_sa_info() is called by ipsec auto --status to display the current
3227 number of transmitted bytes per IPsec SA.
3229 - get_sa_info() is also used by the Dead Peer Detection process to detect
3230 recent ESP activity. If ESP traffic was received from the peer within
3231 the last dpd_delay interval then no R_Y_THERE notification must be sent.
3233 - strongSwan now supports the Relative Distinguished Name "unstructuredName"
3234 in ID_DER_ASN1_DN identities. The following notations are possible:
3236 rightid="unstructuredName=John Doe"
3237 rightid="UN=John Doe"
3239 - fixed a long-standing bug which caused PSK-based roadwarrior connections
3240 to segfault in the function id.c:same_id() called by keys.c:get_secret()
3241 if an FQDN, USER_FQDN, or Key ID was defined, as in the following example.
3248 - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall).
3250 - ipsec starter didn't set host_addr and client.addr ports in whack msg.
3252 - in order to guarantee backwards-compatibility with the script-based
3253 auto function (e.g. auto --replace), the ipsec starter scripts stores
3254 the defaultroute information in the temporary file /var/run/ipsec.info.
3256 - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH
3257 Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config
3260 - the ipsec starter now also recognizes the parameters authby=never and
3261 type=passthrough|pass|drop|reject.
3267 - ipsec starter now supports the also parameter which allows
3268 a modular structure of the connection definitions. Thus
3269 "ipsec start" is now ready to replace "ipsec setup".
3275 - Mathieu Lafon's popular ipsec starter tool has been added to the
3276 strongSwan distribution. Many thanks go to Stephan Scholz from astaro
3277 for his integration work. ipsec starter is a C program which is going
3278 to replace the various shell and awk starter scripts (setup, _plutoload,
3279 _plutostart, _realsetup, _startklips, _confread, and auto). Since
3280 ipsec.conf is now parsed only once, the starting of multiple tunnels is
3281 accelerated tremendously.
3283 - Added support of %defaultroute to the ipsec starter. If the IP address
3284 changes, a HUP signal to the ipsec starter will automatically
3285 reload pluto's connections.
3287 - moved most compile time configurations from pluto/Makefile to
3288 Makefile.inc by defining the options USE_LIBCURL, USE_LDAP,
3289 USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE.
3291 - removed the ipsec verify and ipsec newhostkey commands
3293 - fixed some 64-bit issues in formatted print statements
3295 - The scepclient functionality implementing the Simple Certificate
3296 Enrollment Protocol (SCEP) is nearly complete but hasn't been
3303 - CA certificates are now automatically loaded from a smartcard
3304 or USB crypto token and appear in the ipsec auto --listcacerts
3311 - when using "ipsec whack --scencrypt <data>" with a PKCS#11
3312 library that does not support the C_Encrypt() Cryptoki
3313 function (e.g. OpenSC), the RSA encryption is done in
3314 software using the public key fetched from the smartcard.
3316 - The scepclient function now allows to define the
3317 validity of a self-signed certificate using the --days,
3318 --startdate, and --enddate options. The default validity
3319 has been changed from one year to five years.
3325 - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11
3326 interface to other applications for RSA encryption and decryption
3327 via the whack interface. Notation:
3329 ipsec whack --scencrypt <data>
3330 [--inbase 16|hex|64|base64|256|text|ascii]
3331 [--outbase 16|hex|64|base64|256|text|ascii]
3334 ipsec whack --scdecrypt <data>
3335 [--inbase 16|hex|64|base64|256|text|ascii]
3336 [--outbase 16|hex|64|base64|256|text|ascii]
3339 The default setting for inbase and outbase is hex.
3341 The new proxy interface can be used for securing symmetric
3342 encryption keys required by the cryptoloop or dm-crypt
3343 disk encryption schemes, especially in the case when
3344 pkcs11keepstate=yes causes pluto to lock the pkcs11 slot
3347 - if the file /etc/ipsec.secrets is lacking during the startup of
3348 pluto then the root-readable file /etc/ipsec.d/private/myKey.der
3349 containing a 2048 bit RSA private key and a matching self-signed
3350 certificate stored in the file /etc/ipsec.d/certs/selfCert.der
3351 is automatically generated by calling the function
3353 ipsec scepclient --out pkcs1 --out cert-self
3355 scepclient was written by Jan Hutter and Martin Willi, students
3356 at the University of Applied Sciences in Rapperswil, Switzerland.
3362 - the current extension of the PKCS#7 framework introduced
3363 a parsing error in PKCS#7 wrapped X.509 certificates that are
3364 e.g. transmitted by Windows XP when multi-level CAs are used.
3365 the parsing syntax has been fixed.
3367 - added a patch by Gerald Richter which tolerates multiple occurrences
3368 of the ipsec0 interface when using KLIPS.
3374 - with gawk-3.1.4 the word "default2 has become a protected
3375 keyword for use in switch statements and cannot be used any
3376 more in the strongSwan scripts. This problem has been
3377 solved by renaming "default" to "defaults" and "setdefault"
3378 in the scripts _confread and auto, respectively.
3380 - introduced the parameter leftsendcert with the values
3382 always|yes (the default, always send a cert)
3383 ifasked (send the cert only upon a cert request)
3384 never|no (never send a cert, used for raw RSA keys and
3387 - fixed the initialization of the ESP key length to a default of
3388 128 bits in the case that the peer does not send a key length
3389 attribute for AES encryption.
3391 - applied Herbert Xu's uniqueIDs patch
3393 - applied Herbert Xu's CLOEXEC patches
3399 - CRLs can now be cached also in the case when the issuer's
3400 certificate does not contain a subjectKeyIdentifier field.
3401 In that case the subjectKeyIdentifier is computed by pluto as the
3402 160 bit SHA-1 hash of the issuer's public key in compliance
3403 with section 4.2.1.2 of RFC 3280.
3405 - Fixed a bug introduced by strongswan-2.5.1 which eliminated
3406 not only multiple Quick Modes of a given connection but also
3407 multiple connections between two security gateways.
3413 - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute
3414 installed either by setting auto=route in ipsec.conf or by
3415 a connection put into hold, generates an XFRM_ACQUIRE event
3416 for each packet that wants to use the not-yet existing
3417 tunnel. Up to now each XFRM_ACQUIRE event led to an entry in
3418 the Quick Mode queue, causing multiple IPsec SA to be
3419 established in rapid succession. Starting with strongswan-2.5.1
3420 only a single IPsec SA is established per host-pair connection.
3422 - Right after loading the PKCS#11 module, all smartcard slots are
3423 searched for certificates. The result can be viewed using
3426 ipsec auto --listcards
3428 The certificate objects found in the slots are numbered
3429 starting with #1, #2, etc. This position number can be used to address
3430 certificates (leftcert=%smartcard) and keys (: PIN %smartcard)
3431 in ipsec.conf and ipsec.secrets, respectively:
3433 %smartcard (selects object #1)
3434 %smartcard#1 (selects object #1)
3435 %smartcard#3 (selects object #3)
3437 As an alternative the existing retrieval scheme can be used:
3439 %smartcard:45 (selects object with id=45)
3440 %smartcard0 (selects first object in slot 0)
3441 %smartcard4:45 (selects object in slot 4 with id=45)
3443 - Depending on the settings of CKA_SIGN and CKA_DECRYPT
3444 private key flags either C_Sign() or C_Decrypt() is used
3445 to generate a signature.
3447 - The output buffer length parameter siglen in C_Sign()
3448 is now initialized to the actual size of the output
3449 buffer prior to the function call. This fixes the
3450 CKR_BUFFER_TOO_SMALL error that could occur when using
3451 the OpenSC PKCS#11 module.
3453 - Changed the initialization of the PKCS#11 CK_MECHANISM in
3454 C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }.
3456 - Refactored the RSA public/private key code and transferred it
3457 from keys.c to the new pkcs1.c file as a preparatory step
3458 towards the release of the SCEP client.
3464 - The loading of a PKCS#11 smartcard library module during
3465 runtime does not require OpenSC library functions any more
3466 because the corresponding code has been integrated into
3467 smartcard.c. Also the RSAREF pkcs11 header files have been
3468 included in a newly created pluto/rsaref directory so that
3469 no external include path has to be defined any longer.
3471 - A long-awaited feature has been implemented at last:
3472 The local caching of CRLs fetched via HTTP or LDAP, activated
3473 by the parameter cachecrls=yes in the config setup section
3474 of ipsec.conf. The dynamically fetched CRLs are stored under
3475 a unique file name containing the issuer's subjectKeyID
3476 in /etc/ipsec.d/crls.
3478 - Applied a one-line patch courtesy of Michael Richardson
3479 from the Openswan project which fixes the kernel-oops
3480 in KLIPS when an snmp daemon is running on the same box.
3486 - Eliminated null length CRL distribution point strings.
3488 - Fixed a trust path evaluation bug introduced with 2.4.3
3494 - Improved the joint OCSP / CRL revocation policy.
3495 OCSP responses have precedence over CRL entries.
3497 - Introduced support of CRLv2 reason codes.
3499 - Fixed a bug with key-pad equipped readers which caused
3500 pluto to prompt for the pin via the console when the first
3501 occasion to enter the pin via the key-pad was missed.
3503 - When pluto is built with LDAP_V3 enabled, the library
3504 liblber required by newer versions of openldap is now
3511 - Added the _updown_espmark template which requires all
3512 incoming ESP traffic to be marked with a default mark
3515 - Introduced the pkcs11keepstate parameter in the config setup
3516 section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11
3517 session and login states are kept as long as possible during
3518 the lifetime of pluto. This means that a PIN entry via a key
3519 pad has to be done only once.
3521 - Introduced the pkcs11module parameter in the config setup
3522 section of ipsec.conf which specifies the PKCS#11 module
3523 to be used with smart cards. Example:
3525 pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo
3527 - Added support of smartcard readers equipped with a PIN pad.
3529 - Added patch by Jay Pfeifer which detects when netkey
3530 modules have been statically built into the Linux 2.6 kernel.
3532 - Added two patches by Herbert Xu. The first uses ip xfrm
3533 instead of setkey to flush the IPsec policy database. The
3534 second sets the optional flag in inbound IPComp SAs only.
3536 - Applied Ulrich Weber's patch which fixes an interoperability
3537 problem between native IPsec and KLIPS systems caused by
3538 setting the replay window to 32 instead of 0 for ipcomp.
3544 - Fixed a bug which caused an unwanted Mode Config request
3545 to be initiated in the case where "right" was used to denote
3546 the local side in ipsec.conf and "left" the remote side,
3547 contrary to the recommendation that "right" be remote and
3554 - updated Vendor ID to strongSwan-2.4.0
3556 - updated copyright statement to include David Buechi and
3563 - strongSwan now communicates with attached smartcards and
3564 USB crypto tokens via the standardized PKCS #11 interface.
3565 By default the OpenSC library from www.opensc.org is used
3566 but any other PKCS#11 library could be dynamically linked.
3567 strongSwan's PKCS#11 API was implemented by David Buechi
3568 and Michael Meier, both graduates of the Zurich University
3569 of Applied Sciences in Winterthur, Switzerland.
3571 - When a %trap eroute is triggered by an outgoing IP packet
3572 then the native IPsec stack of the Linux 2.6 kernel [often/
3573 always?] returns an XFRM_ACQUIRE message with an undefined
3574 protocol family field and the connection setup fails.
3575 As a workaround IPv4 (AF_INET) is now assumed.
3577 - the results of the UML test scenarios are now enhanced
3578 with block diagrams of the virtual network topology used
3579 in a particular test.
3585 - fixed IV used to decrypt informational messages.
3586 This bug was introduced with Mode Config functionality.
3588 - fixed NCP Vendor ID.
3590 - undid one of Ulrich Weber's maximum udp size patches
3591 because it caused a segmentation fault with NAT-ed
3594 - added UML scenarios wildcards and attr-cert which
3595 demonstrate the implementation of IPsec policies based
3596 on wildcard parameters contained in Distinguished Names and
3597 on X.509 attribute certificates, respectively.
3603 - Added basic Mode Config functionality
3605 - Added Mathieu Lafon's patch which upgrades the status of
3606 the NAT-Traversal implementation to RFC 3947.
3608 - The _startklips script now also loads the xfrm4_tunnel
3611 - Added Ulrich Weber's netlink replay window size and
3612 maximum udp size patches.
3614 - UML testing now uses the Linux 2.6.10 UML kernel by default.
3620 - Eric Marchionni and Patrik Rayo, both recent graduates from
3621 the Zuercher Hochschule Winterthur in Switzerland, created a
3622 User-Mode-Linux test setup for strongSwan. For more details
3623 please read the INSTALL and README documents in the testing
3626 - Full support of group attributes based on X.509 attribute
3627 certificates. Attribute certificates can be generated
3628 using the openac facility. For more details see
3632 The group attributes can be used in connection definitions
3633 in order to give IPsec access to specific user groups.
3634 This is done with the new parameter left|rightgroups as in
3636 rightgroups="Research, Sales"
3638 giving access to users possessing the group attributes
3639 Research or Sales, only.
3641 - In Quick Mode clients with subnet mask /32 are now
3642 coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should
3643 fix rekeying problems with the SafeNet/SoftRemote and NCP
3644 Secure Entry Clients.
3646 - Changed the defaults of the ikelifetime and keylife parameters
3647 to 3h and 1h, respectively. The maximum allowable values are
3648 now both set to 24 h.
3650 - Suppressed notification wars between two IPsec peers that
3651 could e.g. be triggered by incorrect ISAKMP encryption.
3653 - Public RSA keys can now have identical IDs if either the
3654 issuing CA or the serial number is different. The serial
3655 number of a certificate is now shown by the command
3657 ipsec auto --listpubkeys
3663 - Added Tuomo Soini's sourceip feature which allows a strongSwan
3664 roadwarrior to use a fixed Virtual IP (see README section 2.6)
3665 and reduces the well-known four tunnel case on VPN gateways to
3666 a single tunnel definition (see README section 2.4).
3668 - Fixed a bug occurring with NAT-Traversal enabled when the responder
3669 suddenly turns initiator and the initiator cannot find a matching
3670 connection because of the floated IKE port 4500.
3672 - Removed misleading ipsec verify command from barf.
3674 - Running under the native IP stack, ipsec --version now shows
3675 the Linux kernel version (courtesy to the Openswan project).
3681 - Introduced the ipsec auto --listalgs monitoring command which lists
3682 all currently registered IKE and ESP algorithms.
3684 - Fixed a bug in the ESP algorithm selection occurring when the strict flag
3685 is set and the first proposed transform does not match.
3687 - Fixed another deadlock in the use of the lock_certs_and_keys() mutex,
3688 occurring when a smartcard is present.
3690 - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event.
3692 - Fixed the printing of the notification names (null)
3694 - Applied another of Herbert Xu's Netlink patches.
3700 - Support of Dead Peer Detection. The connection parameter
3702 dpdaction=clear|hold
3704 activates DPD for the given connection.
3706 - The default Opportunistic Encryption (OE) policy groups are not
3707 automatically included anymore. Those wishing to activate OE can include
3708 the policy group with the following statement in ipsec.conf:
3710 include /etc/ipsec.d/examples/oe.conf
3712 The default for [right|left]rsasigkey is now set to %cert.
3714 - strongSwan now has a Vendor ID of its own which can be activated
3715 using the compile option VENDORID
3717 - Applied Herbert Xu's patch which sets the compression algorithm correctly.
3719 - Applied Herbert Xu's patch fixing an ESPINUDP problem
3721 - Applied Herbert Xu's patch setting source/destination port numbers.
3723 - Reapplied one of Herbert Xu's NAT-Traversal patches which got
3724 lost during the migration from SuperFreeS/WAN.
3726 - Fixed a deadlock in the use of the lock_certs_and_keys() mutex.
3728 - Fixed the unsharing of alg parameters when instantiating group
3735 - Thomas Walpuski made me aware of a potential DoS attack via
3736 a PKCS#7-wrapped certificate bundle which could overwrite valid CA
3737 certificates in Pluto's authority certificate store. This vulnerability
3738 was fixed by establishing trust in CA candidate certificates up to a
3739 trusted root CA prior to insertion into Pluto's chained list.
3741 - replaced the --assign option by the -v option in the auto awk script
3742 in order to make it run with mawk under debian/woody.
3748 - Split of the status information between ipsec auto --status (concise)
3749 and ipsec auto --statusall (verbose). Both commands can be used with
3750 an optional connection selector:
3752 ipsec auto --status[all] <connection_name>
3754 - Added the description of X.509 related features to the ipsec_auto(8)
3757 - Hardened the ASN.1 parser in debug mode, especially the printing
3758 of malformed distinguished names.
3760 - The size of an RSA public key received in a certificate is now restricted to
3762 512 bits <= modulus length <= 8192 bits.
3764 - Fixed the debug mode enumeration.
3770 - Fixed another PKCS#7 vulnerability which could lead to an
3771 endless loop while following the X.509 trust chain.
3777 - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski
3778 that accepted end certificates having identical issuer and subject
3779 distinguished names in a multi-tier X.509 trust chain.
3785 - Removed all remaining references to ipsec_netlink.h in KLIPS.
3791 - The new "ca" section allows to define the following parameters:
3794 cacert=koolCA.pem # cacert of kool CA
3795 ocspuri=http://ocsp.kool.net:8001 # ocsp server
3796 ldapserver=ldap.kool.net # default ldap server
3797 crluri=http://www.kool.net/kool.crl # crl distribution point
3798 crluri2="ldap:///O=Kool, C= .." # crl distribution point #2
3799 auto=add # add, ignore
3801 The ca definitions can be monitored via the command
3803 ipsec auto --listcainfos
3805 - Fixed cosmetic corruption of /proc filesystem by integrating
3806 D. Hugh Redelmeier's freeswan-2.06 kernel fixes.
3812 - Added support for the 818043 NAT-Traversal update of Microsoft's
3813 Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode.
3815 - A symbolic link to libcrypto is now added in the kernel sources
3816 during kernel compilation
3818 - Fixed a couple of 64 bit issues (mostly casts to int).
3819 Thanks to Ken Bantoft who checked my sources on a 64 bit platform.
3821 - Replaced s[n]printf() statements in the kernel by ipsec_snprintf().
3822 Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro
3823 of the FreeS/WAN team who solved this problem with the 2.4.25 kernel.
3829 - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName
3830 certificate extension which contains no generalName item) can cause
3831 a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has
3832 been hardened to make it more robust against malformed ASN.1 objects.
3834 - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native
3835 Linux 2.6 IPsec stack.
3841 - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12