4 - Added support for IKEv2 make-before-break reauthentication. By using a global
5 CHILD_SA reqid allocation mechanism, charon supports overlapping CHILD_SAs.
6 This allows the use of make-before-break instead of the previously supported
7 break-before-make reauthentication, avoiding connectivity gaps during that
8 procedure. As the new mechanism may fail with peers not supporting it (such
9 as any previous strongSwan release) it must be explicitly enabled using
10 the charon.make_before_break strongswan.conf option.
12 - Support for "Signature Authentication in IKEv2" (RFC 7427) has been added.
13 This allows the use of stronger hash algorithms for public key authentication.
14 By default, signature schemes are chosen based on the strength of the
15 signature key, but specific hash algorithms may be configured in leftauth.
17 - Key types and hash algorithms specified in rightauth are now also checked
18 against IKEv2 signature schemes. If such constraints are used for certificate
19 chain validation in existing configurations, in particular with peers that
20 don't support RFC 7427, it may be necessary to disable this feature with the
21 charon.signature_authentication_constraints setting, because the signature
22 scheme used in classic IKEv2 public key authentication may not be strong
25 - The new connmark plugin allows a host to bind conntrack flows to a specific
26 CHILD_SA by applying and restoring the SA mark to conntrack entries. This
27 allows a peer to handle multiple transport mode connections coming over the
28 same NAT device for client-initiated flows. A common use case is to protect
29 L2TP/IPsec, as supported by some systems.
31 - The forecast plugin can forward broadcast and multicast messages between
32 connected clients and a LAN. For CHILD_SA using unique marks, it sets up
33 the required Netfilter rules and uses a multicast/broadcast listener that
34 forwards such messages to all connected clients. This plugin is designed for
35 Windows 7 IKEv2 clients, which announces its services over the tunnel if the
36 negotiated IPsec policy allows it.
38 - EAP server methods now can fulfill public key constraints, such as rightcert
39 or rightca. Additionally, public key and signature constraints can be
40 specified for EAP methods in the rightauth keyword. Currently the EAP-TLS and
41 EAP-TTLS methods provide verification details to constraints checking.
43 - Upgrade of the BLISS post-quantum signature algorithm to the improved BLISS-B
44 variant. Can be used in conjunction with the SHA256, SHA384 and SHA512 hash
45 algorithms with SHA512 being the default.
51 - Fixed a denial-of-service vulnerability triggered by an IKEv2 Key Exchange
52 payload that contains the Diffie-Hellman group 1025. This identifier was
53 used internally for DH groups with custom generator and prime. Because
54 these arguments are missing when creating DH objects based on the KE payload
55 an invalid pointer dereference occurred. This allowed an attacker to crash
56 the IKE daemon with a single IKE_SA_INIT message containing such a KE
57 payload. The vulnerability has been registered as CVE-2014-9221.
59 - The left/rightid options in ipsec.conf, or any other identity in strongSwan,
60 now accept prefixes to enforce an explicit type, such as email: or fqdn:.
61 Note that no conversion is done for the remaining string, refer to
62 ipsec.conf(5) for details.
64 - The post-quantum Bimodal Lattice Signature Scheme (BLISS) can be used as
65 an IKEv2 public key authentication method. The pki tool offers full support
66 for the generation of BLISS key pairs and certificates.
68 - Fixed mapping of integrity algorithms negotiated for AH via IKEv1. This could
69 cause interoperability issues when connecting to older versions of charon.
75 - The new charon-systemd IKE daemon implements an IKE daemon tailored for use
76 with systemd. It avoids the dependency on ipsec starter and uses swanctl
77 as configuration backend, building a simple and lightweight solution. It
78 supports native systemd journal logging.
80 - Support for IKEv2 fragmentation as per RFC 7383 has been added. Like IKEv1
81 fragmentation it can be enabled by setting fragmentation=yes in ipsec.conf.
83 - Support of the TCG TNC IF-M Attribute Segmentation specification proposal.
84 All attributes can be segmented. Additionally TCG/SWID Tag, TCG/SWID Tag ID
85 and IETF/Installed Packages attributes can be processed incrementally on a
88 - The new ext-auth plugin calls an external script to implement custom IKE_SA
89 authorization logic, courtesy of Vyronas Tsingaras.
91 - For the vici plugin a ruby gem has been added to allow ruby applications
92 to control or monitor the IKE daemon. The vici documentation has been updated
93 to include a description of the available operations and some simple examples
94 using both the libvici C interface and the ruby gem.
100 - strongSwan has been ported to the Windows platform. Using a MinGW toolchain,
101 many parts of the strongSwan codebase run natively on Windows 7 / 2008 R2
102 and newer releases. charon-svc implements a Windows IKE service based on
103 libcharon, the kernel-iph and kernel-wfp plugins act as networking and IPsec
104 backend on the Windows platform. socket-win provides a native IKE socket
105 implementation, while winhttp fetches CRL and OCSP information using the
108 - The new vici plugin provides a Versatile IKE Configuration Interface for
109 charon. Using the stable IPC interface, external applications can configure,
110 control and monitor the IKE daemon. Instead of scripting the ipsec tool
111 and generating ipsec.conf, third party applications can use the new interface
112 for more control and better reliability.
114 - Built upon the libvici client library, swanctl implements the first user of
115 the VICI interface. Together with a swanctl.conf configuration file,
116 connections can be defined, loaded and managed. swanctl provides a portable,
117 complete IKE configuration and control interface for the command line.
118 The first six swanctl example scenarios have been added.
120 - The SWID IMV implements a JSON-based REST API which allows the exchange
121 of SWID tags and Software IDs with the strongTNC policy manager.
123 - The SWID IMC can extract all installed packages from the dpkg (Debian,
124 Ubuntu, Linux Mint etc.), rpm (Fedora, RedHat, OpenSUSE, etc.), or
125 pacman (Arch Linux, Manjaro, etc.) package managers, respectively, using the
126 swidGenerator (https://github.com/strongswan/swidGenerator) which generates
127 SWID tags according to the new ISO/IEC 19770-2:2014 standard.
129 - All IMVs now share the access requestor ID, device ID and product info
130 of an access requestor via a common imv_session object.
132 - The Attestation IMC/IMV pair supports the IMA-NG measurement format
133 introduced with the Linux 3.13 kernel.
135 - The aikgen tool generates an Attestation Identity Key bound to a TPM.
137 - Implemented the PT-EAP transport protocol (RFC 7171) for Trusted Network
140 - The ipsec.conf replay_window option defines connection specific IPsec replay
141 windows. Original patch courtesy of Zheng Zhong and Christophe Gouault from
148 - Fixed an authentication bypass vulnerability triggered by rekeying an
149 unestablished IKEv2 SA while it gets actively initiated. This allowed an
150 attacker to trick a peer's IKE_SA state to established, without the need to
151 provide any valid authentication credentials. The vulnerability has been
152 registered as CVE-2014-2338.
154 - The acert plugin evaluates X.509 Attribute Certificates. Group membership
155 information encoded as strings can be used to fulfill authorization checks
156 defined with the rightgroups option. Attribute Certificates can be loaded
157 locally or get exchanged in IKEv2 certificate payloads.
159 - The pki command gained support to generate X.509 Attribute Certificates
160 using the --acert subcommand, while the --print command supports the ac type.
161 The openac utility has been removed in favor of the new pki functionality.
163 - The libtls TLS 1.2 implementation as used by EAP-(T)TLS and other protocols
164 has been extended by AEAD mode support, currently limited to AES-GCM.
170 - A new default configuration file layout is introduced. The new default
171 strongswan.conf file mainly includes config snippets from the strongswan.d
172 and strongswan.d/charon directories (the latter containing snippets for all
173 plugins). The snippets, with commented defaults, are automatically
174 generated and installed, if they don't exist yet. They are also installed
175 in $prefix/share/strongswan/templates so existing files can be compared to
176 the current defaults.
178 - As an alternative to the non-extensible charon.load setting, the plugins
179 to load in charon (and optionally other applications) can now be determined
180 via the charon.plugins.<name>.load setting for each plugin (enabled in the
181 new default strongswan.conf file via the charon.load_modular option).
182 The load setting optionally takes a numeric priority value that allows
183 reordering the plugins (otherwise the default plugin order is preserved).
185 - All strongswan.conf settings that were formerly defined in library specific
186 "global" sections are now application specific (e.g. settings for plugins in
187 libstrongswan.plugins can now be set only for charon in charon.plugins).
188 The old options are still supported, which now allows to define defaults for
189 all applications in the libstrongswan section.
191 - The ntru libstrongswan plugin supports NTRUEncrypt as a post-quantum
192 computer IKE key exchange mechanism. The implementation is based on the
193 ntru-crypto library from the NTRUOpenSourceProject. The supported security
194 strengths are ntru112, ntru128, ntru192, and ntru256. Since the private DH
195 group IDs 1030..1033 have been assigned, the strongSwan Vendor ID must be
196 sent (charon.send_vendor_id = yes) in order to use NTRU.
198 - Defined a TPMRA remote attestation workitem and added support for it to the
201 - Compatibility issues between IPComp (compress=yes) and leftfirewall=yes as
202 well as multiple subnets in left|rightsubnet have been fixed.
204 - When enabling its "session" strongswan.conf option, the xauth-pam plugin opens
205 and closes a PAM session for each established IKE_SA. Patch courtesy of
208 - The strongSwan unit testing framework has been rewritten without the "check"
209 dependency for improved flexibility and portability. It now properly supports
210 multi-threaded and memory leak testing and brings a bunch of new test cases.
216 - Fixed a denial-of-service vulnerability and potential authorization bypass
217 triggered by a crafted ID_DER_ASN1_DN ID payload. The cause is an insufficient
218 length check when comparing such identities. The vulnerability has been
219 registered as CVE-2013-6075.
221 - Fixed a denial-of-service vulnerability triggered by a crafted IKEv1
222 fragmentation payload. The cause is a NULL pointer dereference. The
223 vulnerability has been registered as CVE-2013-6076.
225 - The lean stand-alone pt-tls-client can set up a RFC 6876 PT-TLS session
226 with a strongSwan policy enforcement point which uses the tnc-pdp charon
229 - The new TCG TNC SWID IMC/IMV pair supports targeted SWID requests for either
230 full SWID Tag or concise SWID Tag ID inventories.
232 - The XAuth backend in eap-radius now supports multiple XAuth exchanges for
233 different credential types and display messages. All user input gets
234 concatenated and verified with a single User-Password RADIUS attribute on
235 the AAA. With an AAA supporting it, one for example can implement
236 Password+Token authentication with proper dialogs on iOS and OS X clients.
238 - charon supports IKEv1 Mode Config exchange in push mode. The ipsec.conf
239 modeconfig=push option enables it for both client and server, the same way
242 - Using the "ah" ipsec.conf keyword on both IKEv1 and IKEv2 connections,
243 charon can negotiate and install Security Associations integrity-protected by
244 the Authentication Header protocol. Supported are plain AH(+IPComp) SAs only,
245 but not the deprecated RFC2401 style ESP+AH bundles.
247 - The generation of initialization vectors for IKE and ESP (when using libipsec)
248 is now modularized and IVs for e.g. AES-GCM are now correctly allocated
249 sequentially, while other algorithms like AES-CBC still use random IVs.
251 - The left and right options in ipsec.conf can take multiple address ranges
252 and subnets. This allows connection matching against a larger set of
253 addresses, for example to use a different connection for clients connecting
254 from a internal network.
256 - For all those who have a queasy feeling about the NIST elliptic curve set,
257 the Brainpool curves introduced for use with IKE by RFC 6932 might be a
258 more trustworthy alternative.
260 - The kernel-libipsec userland IPsec backend now supports usage statistics,
261 volume based rekeying and accepts ESPv3 style TFC padded packets.
263 - With two new strongswan.conf options fwmarks can be used to implement
264 host-to-host tunnels with kernel-libipsec.
266 - load-tester supports transport mode connections and more complex traffic
267 selectors, including such using unique ports for each tunnel.
269 - The new dnscert plugin provides support for authentication via CERT RRs that
270 are protected via DNSSEC. The plugin was created by Ruslan N. Marchenko.
272 - The eap-radius plugin supports forwarding of several Cisco Unity specific
273 RADIUS attributes in corresponding configuration payloads.
275 - Database transactions are now abstracted and implemented by the two backends.
276 If you use MySQL make sure all tables use the InnoDB engine.
278 - libstrongswan now can provide an experimental custom implementation of the
279 printf family functions based on klibc if neither Vstr nor glibc style printf
280 hooks are available. This can avoid the Vstr dependency on some systems at
281 the cost of slower and less complete printf functions.
287 - Fixed a denial-of-service vulnerability triggered by specific XAuth usernames
288 and EAP identities (since 5.0.3), and PEM files (since 4.1.11). The crash
289 was caused by insufficient error handling in the is_asn1() function.
290 The vulnerability has been registered as CVE-2013-5018.
292 - The new charon-cmd command line IKE client can establish road warrior
293 connections using IKEv1 or IKEv2 with different authentication profiles.
294 It does not depend on any configuration files and can be configured using a
295 few simple command line options.
297 - The kernel-pfroute networking backend has been greatly improved. It now
298 can install virtual IPs on TUN devices on OS X and FreeBSD, allowing these
299 systems to act as a client in common road warrior scenarios.
301 - The new kernel-libipsec plugin uses TUN devices and libipsec to provide IPsec
302 processing in userland on Linux, FreeBSD and Mac OS X.
304 - The eap-radius plugin can now serve as an XAuth backend called xauth-radius,
305 directly verifying XAuth credentials using RADIUS User-Name/User-Password
306 attributes. This is more efficient than the existing xauth-eap+eap-radius
307 combination, and allows RADIUS servers without EAP support to act as AAA
310 - The new osx-attr plugin installs configuration attributes (currently DNS
311 servers) via SystemConfiguration on Mac OS X. The keychain plugin provides
312 certificates from the OS X keychain service.
314 - The sshkey plugin parses SSH public keys, which, together with the --agent
315 option for charon-cmd, allows the use of ssh-agent for authentication.
316 To configure SSH keys in ipsec.conf the left|rightrsasigkey options are
317 replaced with left|rightsigkey, which now take public keys in one of three
318 formats: SSH (RFC 4253, ssh: prefix), DNSKEY (RFC 3110, dns: prefix), and
319 PKCS#1 (the default, no prefix).
321 - Extraction of certificates and private keys from PKCS#12 files is now provided
322 by the new pkcs12 plugin or the openssl plugin. charon-cmd (--p12) as well
323 as charon (via P12 token in ipsec.secrets) can make use of this.
325 - IKEv2 can now negotiate transport mode and IPComp in NAT situations.
327 - IKEv2 exchange initiators now properly close an established IKE or CHILD_SA
328 on error conditions using an additional exchange, keeping state in sync
331 - Using a SQL database interface a Trusted Network Connect (TNC) Policy Manager
332 can generate specific measurement workitems for an arbitrary number of
333 Integrity Measurement Verifiers (IMVs) based on the history of the VPN user
336 - Several core classes in libstrongswan are now tested with unit tests. These
337 can be enabled with --enable-unit-tests and run with 'make check'. Coverage
338 reports can be generated with --enable-coverage and 'make coverage' (this
339 disables any optimization, so it should not be enabled when building
340 production releases).
342 - The leak-detective developer tool has been greatly improved. It works much
343 faster/stabler with multiple threads, does not use deprecated malloc hooks
344 anymore and has been ported to OS X.
346 - chunk_hash() is now based on SipHash-2-4 with a random key. This provides
347 better distribution and prevents hash flooding attacks when used with
350 - All default plugins implement the get_features() method to define features
351 and their dependencies. The plugin loader has been improved, so that plugins
352 in a custom load statement can be ordered freely or to express preferences
353 without being affected by dependencies between plugin features.
355 - A centralized thread can take care for watching multiple file descriptors
356 concurrently. This removes the need for a dedicated listener threads in
357 various plugins. The number of "reserved" threads for such tasks has been
358 reduced to about five, depending on the plugin configuration.
360 - Plugins that can be controlled by a UNIX socket IPC mechanism gained network
361 transparency. Third party applications querying these plugins now can use
362 TCP connections from a different host.
364 - libipsec now supports AES-GCM.
370 - Fixed a security vulnerability in the openssl plugin which was reported by
371 Kevin Wojtysiak. The vulnerability has been registered as CVE-2013-2944.
372 Before the fix, if the openssl plugin's ECDSA signature verification was used,
373 due to a misinterpretation of the error code returned by the OpenSSL
374 ECDSA_verify() function, an empty or zeroed signature was accepted as a
377 - The handling of a couple of other non-security relevant openssl return codes
380 - The tnc_ifmap plugin now publishes virtual IPv4 and IPv6 addresses via its
381 TCG TNC IF-MAP 2.1 interface.
383 - The charon.initiator_only option causes charon to ignore IKE initiation
386 - The openssl plugin can now use the openssl-fips library.
392 - The new ipseckey plugin enables authentication based on trustworthy public
393 keys stored as IPSECKEY resource records in the DNS and protected by DNSSEC.
394 To do so it uses a DNSSEC enabled resolver, like the one provided by the new
395 unbound plugin, which is based on libldns and libunbound. Both plugins were
396 created by Reto Guadagnini.
398 - Implemented the TCG TNC IF-IMV 1.4 draft making access requestor identities
399 available to an IMV. The OS IMV stores the AR identity together with the
400 device ID in the attest database.
402 - The openssl plugin now uses the AES-NI accelerated version of AES-GCM
403 if the hardware supports it.
405 - The eap-radius plugin can now assign virtual IPs to IKE clients using the
406 Framed-IP-Address attribute by using the "%radius" named pool in the
407 rightsourceip ipsec.conf option. Cisco Banner attributes are forwarded to
408 Unity-capable IKEv1 clients during mode config. charon now sends Interim
409 Accounting updates if requested by the RADIUS server, reports
410 sent/received packets in Accounting messages, and adds a Terminate-Cause
413 - The recently introduced "ipsec listcounters" command can report connection
414 specific counters by passing a connection name, and global or connection
415 counters can be reset by the "ipsec resetcounters" command.
417 - The strongSwan libpttls library provides an experimental implementation of
418 PT-TLS (RFC 6876), a Posture Transport Protocol over TLS.
420 - The charon systime-fix plugin can disable certificate lifetime checks on
421 embedded systems if the system time is obviously out of sync after bootup.
422 Certificates lifetimes get checked once the system time gets sane, closing
423 or reauthenticating connections using expired certificates.
425 - The "ikedscp" ipsec.conf option can set DiffServ code points on outgoing
428 - The new xauth-noauth plugin allows to use basic RSA or PSK authentication with
429 clients that cannot be configured without XAuth authentication. The plugin
430 simply concludes the XAuth exchange successfully without actually performing
431 any authentication. Therefore, to use this backend it has to be selected
432 explicitly with rightauth2=xauth-noauth.
434 - The new charon-tkm IKEv2 daemon delegates security critical operations to a
435 separate process. This has the benefit that the network facing daemon has no
436 knowledge of keying material used to protect child SAs. Thus subverting
437 charon-tkm does not result in the compromise of cryptographic keys.
438 The extracted functionality has been implemented from scratch in a minimal TCB
439 (trusted computing base) in the Ada programming language. Further information
440 can be found at http://www.codelabs.ch/tkm/.
445 - Implemented all IETF Standard PA-TNC attributes and an OS IMC/IMV
446 pair using them to transfer operating system information.
448 - The new "ipsec listcounters" command prints a list of global counter values
449 about received and sent IKE messages and rekeyings.
451 - A new lookip plugin can perform fast lookup of tunnel information using a
452 clients virtual IP and can send notifications about established or deleted
453 tunnels. The "ipsec lookip" command can be used to query such information
454 or receive notifications.
456 - The new error-notify plugin catches some common error conditions and allows
457 an external application to receive notifications for them over a UNIX socket.
459 - IKE proposals can now use a PRF algorithm different to that defined for
460 integrity protection. If an algorithm with a "prf" prefix is defined
461 explicitly (such as prfsha1 or prfsha256), no implicit PRF algorithm based on
462 the integrity algorithm is added to the proposal.
464 - The pkcs11 plugin can now load leftcert certificates from a smartcard for a
465 specific ipsec.conf conn section and cacert CA certificates for a specific ca
468 - The load-tester plugin gained additional options for certificate generation
469 and can load keys and multiple CA certificates from external files. It can
470 install a dedicated outer IP address for each tunnel and tunnel initiation
471 batches can be triggered and monitored externally using the
472 "ipsec load-tester" tool.
474 - PKCS#7 container parsing has been modularized, and the openssl plugin
475 gained an alternative implementation to decrypt and verify such files.
476 In contrast to our own DER parser, OpenSSL can handle BER files, which is
477 required for interoperability of our scepclient with EJBCA.
479 - Support for the proprietary IKEv1 fragmentation extension has been added.
480 Fragments are always handled on receipt but only sent if supported by the peer
481 and if enabled with the new fragmentation ipsec.conf option.
483 - IKEv1 in charon can now parse certificates received in PKCS#7 containers and
484 supports NAT traversal as used by Windows clients. Patches courtesy of
487 - The new rdrand plugin provides a high quality / high performance random
488 source using the Intel rdrand instruction found on Ivy Bridge processors.
490 - The integration test environment was updated and now uses KVM and reproducible
491 guest images based on Debian.
497 - Introduced the sending of the standard IETF Assessment Result
498 PA-TNC attribute by all strongSwan Integrity Measurement Verifiers.
500 - Extended PTS Attestation IMC/IMV pair to provide full evidence of
501 the Linux IMA measurement process. All pertinent file information
502 of a Linux OS can be collected and stored in an SQL database.
504 - The PA-TNC and PB-TNC protocols can now process huge data payloads
505 >64 kB by distributing PA-TNC attributes over multiple PA-TNC messages
506 and these messages over several PB-TNC batches. As long as no
507 consolidated recommandation from all IMVs can be obtained, the TNC
508 server requests more client data by sending an empty SDATA batch.
510 - The rightgroups2 ipsec.conf option can require group membership during
511 a second authentication round, for example during XAuth authentication
512 against a RADIUS server.
514 - The xauth-pam backend can authenticate IKEv1 XAuth and Hybrid authenticated
515 clients against any PAM service. The IKEv2 eap-gtc plugin does not use
516 PAM directly anymore, but can use any XAuth backend to verify credentials,
519 - The new unity plugin brings support for some parts of the IKEv1 Cisco Unity
520 Extension. As client, charon narrows traffic selectors to the received
521 Split-Include attributes and automatically installs IPsec bypass policies
522 for received Local-LAN attributes. As server, charon sends Split-Include
523 attributes for leftsubnet definitions containing multiple subnets to Unity-
526 - An EAP-Nak payload is returned by clients if the gateway requests an EAP
527 method that the client does not support. Clients can also request a specific
528 EAP method by configuring that method with leftauth.
530 - The eap-dynamic plugin handles EAP-Nak payloads returned by clients and uses
531 these to select a different EAP method supported/requested by the client.
532 The plugin initially requests the first registered method or the first method
533 configured with charon.plugins.eap-dynamic.preferred.
535 - The new left/rightdns options specify connection specific DNS servers to
536 request/respond in IKEv2 configuration payloads or IKEv2 mode config. leftdns
537 can be any (comma separated) combination of %config4 and %config6 to request
538 multiple servers, both for IPv4 and IPv6. rightdns takes a list of DNS server
539 IP addresses to return.
541 - The left/rightsourceip options now accept multiple addresses or pools.
542 leftsourceip can be any (comma separated) combination of %config4, %config6
543 or fixed IP addresses to request. rightsourceip accepts multiple explicitly
544 specified or referenced named pools.
546 - Multiple connections can now share a single address pool when they use the
547 same definition in one of the rightsourceip pools.
549 - The options charon.interfaces_ignore and charon.interfaces_use allow one to
550 configure the network interfaces used by the daemon.
552 - The kernel-netlink plugin supports the charon.install_virtual_ip_on option,
553 which specifies the interface on which virtual IP addresses will be installed.
554 If it is not specified the current behavior of using the outbound interface
557 - The kernel-netlink plugin tries to keep the current source address when
558 looking for valid routes to reach other hosts.
560 - The autotools build has been migrated to use a config.h header. strongSwan
561 development headers will get installed during "make install" if
562 --with-dev-headers has been passed to ./configure.
564 - All crypto primitives gained return values for most operations, allowing
565 crypto backends to fail, for example when using hardware accelerators.
571 - The charon IKE daemon gained experimental support for the IKEv1 protocol.
572 Pluto has been removed from the 5.x series, and unless strongSwan is
573 configured with --disable-ikev1 or --disable-ikev2, charon handles both
574 keying protocols. The feature-set of IKEv1 in charon is almost on par with
575 pluto, but currently does not support AH or bundled AH+ESP SAs. Beside
576 RSA/ECDSA, PSK and XAuth, charon also supports the Hybrid authentication
577 mode. Informations for interoperability and migration is available at
578 http://wiki.strongswan.org/projects/strongswan/wiki/CharonPlutoIKEv1.
580 - Charon's bus_t has been refactored so that loggers and other listeners are
581 now handled separately. The single lock was previously cause for deadlocks
582 if extensive listeners, such as the one provided by the updown plugin, wanted
583 to acquire locks that were held by other threads which in turn tried to log
584 messages, and thus were waiting to acquire the same lock currently held by
585 the thread calling the listener.
586 The implemented changes also allow the use of a read/write-lock for the
587 loggers which increases performance if multiple loggers are registered.
588 Besides several interface changes this last bit also changes the semantics
589 for loggers as these may now be called by multiple threads at the same time.
591 - Source routes are reinstalled if interfaces are reactivated or IP addresses
594 - The thread pool (processor_t) now has more control over the lifecycle of
595 a job (see job.h for details). In particular, it now controls the destruction
596 of jobs after execution and the cancellation of jobs during shutdown. Due to
597 these changes the requeueing feature, previously available to callback_job_t
598 only, is now available to all jobs (in addition to a new rescheduling
601 - In addition to trustchain key strength definitions for different public key
602 systems, the rightauth option now takes a list of signature hash algorithms
603 considered save for trustchain validation. For example, the setting
604 rightauth=rsa-2048-ecdsa-256-sha256-sha384-sha512 requires a trustchain
605 that uses at least RSA-2048 or ECDSA-256 keys and certificate signatures
606 using SHA-256 or better.
612 - Fixed a security vulnerability in the gmp plugin. If this plugin was used
613 for RSA signature verification an empty or zeroed signature was handled as
616 - Fixed several issues with reauthentication and address updates.
622 - The tnc-pdp plugin implements a RADIUS server interface allowing
623 a strongSwan TNC server to act as a Policy Decision Point.
625 - The eap-radius authentication backend enforces Session-Timeout attributes
626 using RFC4478 repeated authentication and acts upon RADIUS Dynamic
627 Authorization extensions, RFC 5176. Currently supported are disconnect
628 requests and CoA messages containing a Session-Timeout.
630 - The eap-radius plugin can forward arbitrary RADIUS attributes from and to
631 clients using custom IKEv2 notify payloads. The new radattr plugin reads
632 attributes to include from files and prints received attributes to the
635 - Added support for untruncated MD5 and SHA1 HMACs in ESP as used in
638 - The cmac plugin implements the AES-CMAC-96 and AES-CMAC-PRF-128 algorithms
639 as defined in RFC 4494 and RFC 4615, respectively.
641 - The resolve plugin automatically installs nameservers via resolvconf(8),
642 if it is installed, instead of modifying /etc/resolv.conf directly.
644 - The IKEv2 charon daemon supports now raw RSA public keys in RFC 3110
645 DNSKEY and PKCS#1 file format.
651 - Upgraded the TCG IF-IMC and IF-IMV C API to the upcoming version 1.3
652 which supports IF-TNCCS 2.0 long message types, the exclusive flags
653 and multiple IMC/IMV IDs. Both the TNC Client and Server as well as
654 the "Test", "Scanner", and "Attestation" IMC/IMV pairs were updated.
656 - Fully implemented the "TCG Attestation PTS Protocol: Binding to IF-M"
657 standard (TLV-based messages only). TPM-based remote attestation of
658 Linux IMA (Integrity Measurement Architecture) possible. Measurement
659 reference values are automatically stored in an SQLite database.
661 - The EAP-RADIUS authentication backend supports RADIUS accounting. It sends
662 start/stop messages containing Username, Framed-IP and Input/Output-Octets
663 attributes and has been tested against FreeRADIUS and Microsoft NPS.
665 - Added support for PKCS#8 encoded private keys via the libstrongswan
666 pkcs8 plugin. This is the default format used by some OpenSSL tools since
667 version 1.0.0 (e.g. openssl req with -keyout).
669 - Added session resumption support to the strongSwan TLS stack.
675 - Because of changing checksums before and after installation which caused
676 the integrity tests to fail we avoided directly linking libsimaka, libtls and
677 libtnccs to those libcharon plugins which make use of these dynamic libraries.
678 Instead we linked the libraries to the charon daemon. Unfortunately Ubuntu
679 11.10 activated the --as-needed ld option which discards explicit links
680 to dynamic libraries that are not actually used by the charon daemon itself,
681 thus causing failures during the loading of the plugins which depend on these
682 libraries for resolving external symbols.
684 - Therefore our approach of computing integrity checksums for plugins had to be
685 changed radically by moving the hash generation from the compilation to the
686 post-installation phase.
692 - The new libstrongswan certexpire plugin collects expiration information of
693 all used certificates and exports them to CSV files. It either directly
694 exports them or uses cron style scheduling for batch exports.
696 - starter passes unresolved hostnames to charon, allowing it to do name
697 resolution not before the connection attempt. This is especially useful with
698 connections between hosts using dynamic IP addresses. Thanks to Mirko Parthey
699 for the initial patch.
701 - The android plugin can now be used without the Android frontend patch and
702 provides DNS server registration and logging to logcat.
704 - Pluto and starter (plus stroke and whack) have been ported to Android.
706 - Support for ECDSA private and public key operations has been added to the
707 pkcs11 plugin. The plugin now also provides DH and ECDH via PKCS#11 and can
708 use tokens as random number generators (RNG). By default only private key
709 operations are enabled, more advanced features have to be enabled by their
710 option in strongswan.conf. This also applies to public key operations (even
711 for keys not stored on the token) which were enabled by default before.
713 - The libstrongswan plugin system now supports detailed plugin dependencies.
714 Many plugins have been extended to export its capabilities and requirements.
715 This allows the plugin loader to resolve plugin loading order automatically,
716 and in future releases, to dynamically load the required features on demand.
717 Existing third party plugins are source (but not binary) compatible if they
718 properly initialize the new get_features() plugin function to NULL.
720 - The tnc-ifmap plugin implements a TNC IF-MAP 2.0 client which can deliver
721 metadata about IKE_SAs via a SOAP interface to a MAP server. The tnc-ifmap
722 plugin requires the Apache Axis2/C library.
728 - Our private libraries (e.g. libstrongswan) are not installed directly in
729 prefix/lib anymore. Instead a subdirectory is used (prefix/lib/ipsec/ by
730 default). The plugins directory is also moved from libexec/ipsec/ to that
733 - The dynamic IMC/IMV libraries were moved from the plugins directory to
734 a new imcvs directory in the prefix/lib/ipsec/ subdirectory.
736 - Job priorities were introduced to prevent thread starvation caused by too
737 many threads handling blocking operations (such as CRL fetching). Refer to
738 strongswan.conf(5) for details.
740 - Two new strongswan.conf options allow to fine-tune performance on IKEv2
741 gateways by dropping IKE_SA_INIT requests on high load.
743 - IKEv2 charon daemon supports start PASS and DROP shunt policies
744 preventing traffic to go through IPsec connections. Installation of the
745 shunt policies either via the XFRM netfilter or PFKEYv2 IPsec kernel
748 - The history of policies installed in the kernel is now tracked so that e.g.
749 trap policies are correctly updated when reauthenticated SAs are terminated.
751 - IMC/IMV Scanner pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
752 Using "netstat -l" the IMC scans open listening ports on the TNC client
753 and sends a port list to the IMV which based on a port policy decides if
754 the client is admitted to the network.
755 (--enable-imc-scanner/--enable-imv-scanner).
757 - IMC/IMV Test pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
758 (--enable-imc-test/--enable-imv-test).
760 - The IKEv2 close action does not use the same value as the ipsec.conf dpdaction
761 setting, but the value defined by its own closeaction keyword. The action
762 is triggered if the remote peer closes a CHILD_SA unexpectedly.
768 - The whitelist plugin for the IKEv2 daemon maintains an in-memory identity
769 whitelist. Any connection attempt of peers not whitelisted will get rejected.
770 The 'ipsec whitelist' utility provides a simple command line frontend for
771 whitelist administration.
773 - The duplicheck plugin provides a specialized form of duplicate checking,
774 doing a liveness check on the old SA and optionally notify a third party
775 application about detected duplicates.
777 - The coupling plugin permanently couples two or more devices by limiting
778 authentication to previously used certificates.
780 - In the case that the peer config and child config don't have the same name
781 (usually in SQL database defined connections), ipsec up|route <peer config>
782 starts|routes all associated child configs and ipsec up|route <child config>
783 only starts|routes the specific child config.
785 - fixed the encoding and parsing of X.509 certificate policy statements (CPS).
787 - Duncan Salerno contributed the eap-sim-pcsc plugin implementing a
788 pcsc-lite based SIM card backend.
790 - The eap-peap plugin implements the EAP PEAP protocol. Interoperates
791 successfully with a FreeRADIUS server and Windows 7 Agile VPN clients.
793 - The IKEv2 daemon charon rereads strongswan.conf on SIGHUP and instructs
794 all plugins to reload. Currently only the eap-radius and the attr plugins
795 support configuration reloading.
797 - Added userland support to the IKEv2 daemon for Extended Sequence Numbers
798 support coming with Linux 2.6.39. To enable ESN on a connection, add
799 the 'esn' keyword to the proposal. The default proposal uses 32-bit sequence
800 numbers only ('noesn'), and the same value is used if no ESN mode is
801 specified. To negotiate ESN support with the peer, include both, e.g.
802 esp=aes128-sha1-esn-noesn.
804 - In addition to ESN, Linux 2.6.39 gained support for replay windows larger
805 than 32 packets. The new global strongswan.conf option 'charon.replay_window'
806 configures the size of the replay window, in packets.
812 - Sansar Choinyambuu implemented the RFC 5793 Posture Broker Protocol (BP)
813 compatible with Trusted Network Connect (TNC). The TNCCS 2.0 protocol
814 requires the tnccs_20, tnc_imc and tnc_imv plugins but does not depend
815 on the libtnc library. Any available IMV/IMC pairs conforming to the
816 Trusted Computing Group's TNC-IF-IMV/IMC 1.2 interface specification
817 can be loaded via /etc/tnc_config.
819 - Re-implemented the TNCCS 1.1 protocol by using the tnc_imc and tnc_imv
820 in place of the external libtnc library.
822 - The tnccs_dynamic plugin loaded on a TNC server in addition to the
823 tnccs_11 and tnccs_20 plugins, dynamically detects the IF-TNCCS
824 protocol version used by a TNC client and invokes an instance of
825 the corresponding protocol stack.
827 - IKE and ESP proposals can now be stored in an SQL database using a
828 new proposals table. The start_action field in the child_configs
829 tables allows the automatic starting or routing of connections stored
832 - The new certificate_authorities and certificate_distribution_points
833 tables make it possible to store CRL and OCSP Certificate Distribution
834 points in an SQL database.
836 - The new 'include' statement allows to recursively include other files in
837 strongswan.conf. Existing sections and values are thereby extended and
838 replaced, respectively.
840 - Due to the changes in the parser for strongswan.conf, the configuration
841 syntax for the attr plugin has changed. Previously, it was possible to
842 specify multiple values of a specific attribute type by adding multiple
843 key/value pairs with the same key (e.g. dns) to the plugins.attr section.
844 Because values with the same key now replace previously defined values
845 this is not possible anymore. As an alternative, multiple values can be
846 specified by separating them with a comma (e.g. dns = 1.2.3.4, 2.3.4.5).
848 - ipsec listalgs now appends (set in square brackets) to each crypto
849 algorithm listed the plugin that registered the function.
851 - Traffic Flow Confidentiality padding supported with Linux 2.6.38 can be used
852 by the IKEv2 daemon. The ipsec.conf 'tfc' keyword pads all packets to a given
853 boundary, the special value '%mtu' pads all packets to the path MTU.
855 - The new af-alg plugin can use various crypto primitives of the Linux Crypto
856 API using the AF_ALG interface introduced with 2.6.38. This removes the need
857 for additional userland implementations of symmetric cipher, hash, hmac and
860 - The IKEv2 daemon supports the INITIAL_CONTACT notify as initiator and
861 responder. The notify is sent when initiating configurations with a unique
862 policy, set in ipsec.conf via the global 'uniqueids' option.
864 - The conftest conformance testing framework enables the IKEv2 stack to perform
865 many tests using a distinct tool and configuration frontend. Various hooks
866 can alter reserved bits, flags, add custom notifies and proposals, reorder
867 or drop messages and much more. It is enabled using the --enable-conftest
870 - The new libstrongswan constraints plugin provides advanced X.509 constraint
871 checking. In addition to X.509 pathLen constraints, the plugin checks for
872 nameConstraints and certificatePolicies, including policyMappings and
873 policyConstraints. The x509 certificate plugin and the pki tool have been
874 enhanced to support these extensions. The new left/rightcertpolicy ipsec.conf
875 connection keywords take OIDs a peer certificate must have.
877 - The left/rightauth ipsec.conf keywords accept values with a minimum strength
878 for trustchain public keys in bits, such as rsa-2048 or ecdsa-256.
880 - The revocation and x509 libstrongswan plugins and the pki tool gained basic
881 support for delta CRLs.
887 - IMPORTANT: the default keyexchange mode 'ike' is changing with release 4.5
888 from 'ikev1' to 'ikev2', thus commemorating the five year anniversary of the
889 IKEv2 RFC 4306 and its mature successor RFC 5996. The time has definitively
890 come for IKEv1 to go into retirement and to cede its place to the much more
891 robust, powerful and versatile IKEv2 protocol!
893 - Added new ctr, ccm and gcm plugins providing Counter, Counter with CBC-MAC
894 and Galois/Counter Modes based on existing CBC implementations. These
895 new plugins bring support for AES and Camellia Counter and CCM algorithms
896 and the AES GCM algorithms for use in IKEv2.
898 - The new pkcs11 plugin brings full Smartcard support to the IKEv2 daemon and
899 the pki utility using one or more PKCS#11 libraries. It currently supports
900 RSA private and public key operations and loads X.509 certificates from
903 - Implemented a general purpose TLS stack based on crypto and credential
904 primitives of libstrongswan. libtls supports TLS versions 1.0, 1.1 and 1.2,
905 ECDHE-ECDSA/RSA, DHE-RSA and RSA key exchange algorithms and RSA/ECDSA based
906 client authentication.
908 - Based on libtls, the eap-tls plugin brings certificate based EAP
909 authentication for client and server. It is compatible to Windows 7 IKEv2
910 Smartcard authentication and the OpenSSL based FreeRADIUS EAP-TLS backend.
912 - Implemented the TNCCS 1.1 Trusted Network Connect protocol using the
913 libtnc library on the strongSwan client and server side via the tnccs_11
914 plugin and optionally connecting to a TNC@FHH-enhanced FreeRADIUS AAA server.
915 Depending on the resulting TNC Recommendation, strongSwan clients are granted
916 access to a network behind a strongSwan gateway (allow), are put into a
917 remediation zone (isolate) or are blocked (none), respectively. Any number
918 of Integrity Measurement Collector/Verifier pairs can be attached
919 via the tnc-imc and tnc-imv charon plugins.
921 - The IKEv1 daemon pluto now uses the same kernel interfaces as the IKEv2
922 daemon charon. As a result of this, pluto now supports xfrm marks which
923 were introduced in charon with 4.4.1.
925 - Applets for Maemo 5 (Nokia) allow to easily configure and control IKEv2
926 based VPN connections with EAP authentication on supported devices.
928 - The RADIUS plugin eap-radius now supports multiple RADIUS servers for
929 redundant setups. Servers are selected by a defined priority, server load and
932 - The simple led plugin controls hardware LEDs through the Linux LED subsystem.
933 It currently shows activity of the IKE daemon and is a good example how to
934 implement a simple event listener.
936 - Improved MOBIKE behavior in several corner cases, for instance, if the
937 initial responder moves to a different address.
939 - Fixed left-/rightnexthop option, which was broken since 4.4.0.
941 - Fixed a bug not releasing a virtual IP address to a pool if the XAUTH
942 identity was different from the IKE identity.
944 - Fixed the alignment of ModeConfig messages on 4-byte boundaries in the
945 case where the attributes are not a multiple of 4 bytes (e.g. Cisco's
948 - Fixed the interoperability of the socket_raw and socket_default
951 - Added man page for strongswan.conf
957 - Support of xfrm marks in IPsec SAs and IPsec policies introduced
958 with the Linux 2.6.34 kernel. For details see the example scenarios
959 ikev2/nat-two-rw-mark, ikev2/rw-nat-mark-in-out and ikev2/net2net-psk-dscp.
961 - The PLUTO_MARK_IN and PLUTO_ESP_ENC environment variables can be used
962 in a user-specific updown script to set marks on inbound ESP or
965 - The openssl plugin now supports X.509 certificate and CRL functions.
967 - OCSP/CRL checking in IKEv2 has been moved to the revocation plugin, enabled
968 by default. Plase update manual load directives in strongswan.conf.
970 - RFC3779 ipAddrBlock constraint checking has been moved to the addrblock
971 plugin, disabled by default. Enable it and update manual load directives
972 in strongswan.conf, if required.
974 - The pki utility supports CRL generation using the --signcrl command.
976 - The ipsec pki --self, --issue and --req commands now support output in
977 PEM format using the --outform pem option.
979 - The major refactoring of the IKEv1 Mode Config functionality now allows
980 the transport and handling of any Mode Config attribute.
982 - The RADIUS proxy plugin eap-radius now supports multiple servers. Configured
983 servers are chosen randomly, with the option to prefer a specific server.
984 Non-responding servers are degraded by the selection process.
986 - The ipsec pool tool manages arbitrary configuration attributes stored
987 in an SQL database. ipsec pool --help gives the details.
989 - The new eap-simaka-sql plugin acts as a backend for EAP-SIM and EAP-AKA,
990 reading triplets/quintuplets from an SQL database.
992 - The High Availability plugin now supports a HA enabled in-memory address
993 pool and Node reintegration without IKE_SA rekeying. The latter allows
994 clients without IKE_SA rekeying support to keep connected during
995 reintegration. Additionally, many other issues have been fixed in the ha
998 - Fixed a potential remote code execution vulnerability resulting from
999 the misuse of snprintf(). The vulnerability is exploitable by
1000 unauthenticated users.
1006 - The IKEv2 High Availability plugin has been integrated. It provides
1007 load sharing and failover capabilities in a cluster of currently two nodes,
1008 based on an extend ClusterIP kernel module. More information is available at
1009 http://wiki.strongswan.org/projects/strongswan/wiki/HighAvailability.
1010 The development of the High Availability functionality was sponsored by
1011 secunet Security Networks AG.
1013 - Added IKEv1 and IKEv2 configuration support for the AES-GMAC
1014 authentication-only ESP cipher. Our aes_gmac kernel patch or a Linux
1015 2.6.34 kernel is required to make AES-GMAC available via the XFRM
1018 - Added support for Diffie-Hellman groups 22, 23 and 24 to the gmp, gcrypt
1019 and openssl plugins, usable by both pluto and charon. The new proposal
1020 keywords are modp1024s160, modp2048s224 and modp2048s256. Thanks to Joy Latten
1021 from IBM for his contribution.
1023 - The IKEv1 pluto daemon supports RAM-based virtual IP pools using
1024 the rightsourceip directive with a subnet from which addresses
1027 - The ipsec pki --gen and --pub commands now allow the output of
1028 private and public keys in PEM format using the --outform pem
1029 command line option.
1031 - The new DHCP plugin queries virtual IP addresses for clients from a DHCP
1032 server using broadcasts, or a defined server using the
1033 charon.plugins.dhcp.server strongswan.conf option. DNS/WINS server information
1034 is additionally served to clients if the DHCP server provides such
1035 information. The plugin is used in ipsec.conf configurations having
1036 rightsourceip set to %dhcp.
1038 - A new plugin called farp fakes ARP responses for virtual IP addresses
1039 handed out to clients from the IKEv2 daemon charon. The plugin lets a
1040 road-warrior act as a client on the local LAN if it uses a virtual IP
1041 from the responders subnet, e.g. acquired using the DHCP plugin.
1043 - The existing IKEv2 socket implementations have been migrated to the
1044 socket-default and the socket-raw plugins. The new socket-dynamic plugin
1045 binds sockets dynamically to ports configured via the left-/rightikeport
1046 ipsec.conf connection parameters.
1048 - The android charon plugin stores received DNS server information as "net.dns"
1049 system properties, as used by the Android platform.
1055 - The IKEv2 daemon supports RFC 3779 IP address block constraints
1056 carried as a critical X.509v3 extension in the peer certificate.
1058 - The ipsec pool --add|del dns|nbns command manages DNS and NBNS name
1059 server entries that are sent via the IKEv1 Mode Config or IKEv2
1060 Configuration Payload to remote clients.
1062 - The Camellia cipher can be used as an IKEv1 encryption algorithm.
1064 - The IKEv1 and IKEV2 daemons now check certificate path length constraints.
1066 - The new ipsec.conf conn option "inactivity" closes a CHILD_SA if no traffic
1067 was sent or received within the given interval. To close the complete IKE_SA
1068 if its only CHILD_SA was inactive, set the global strongswan.conf option
1069 "charon.inactivity_close_ike" to yes.
1071 - More detailed IKEv2 EAP payload information in debug output
1073 - IKEv2 EAP-SIM and EAP-AKA share joint libsimaka library
1075 - Added required userland changes for proper SHA256 and SHA384/512 in ESP that
1076 will be introduced with Linux 2.6.33. The "sha256"/"sha2_256" keyword now
1077 configures the kernel with 128 bit truncation, not the non-standard 96
1078 bit truncation used by previous releases. To use the old 96 bit truncation
1079 scheme, the new "sha256_96" proposal keyword has been introduced.
1081 - Fixed IPComp in tunnel mode, stripping out the duplicated outer header. This
1082 change makes IPcomp tunnel mode connections incompatible with previous
1083 releases; disable compression on such tunnels.
1085 - Fixed BEET mode connections on recent kernels by installing SAs with
1086 appropriate traffic selectors, based on a patch by Michael Rossberg.
1088 - Using extensions (such as BEET mode) and crypto algorithms (such as twofish,
1089 serpent, sha256_96) allocated in the private use space now require that we
1090 know its meaning, i.e. we are talking to strongSwan. Use the new
1091 "charon.send_vendor_id" option in strongswan.conf to let the remote peer know
1094 - Experimental support for draft-eronen-ipsec-ikev2-eap-auth, where the
1095 responder omits public key authentication in favor of a mutual authentication
1096 method. To enable EAP-only authentication, set rightauth=eap on the responder
1097 to rely only on the MSK constructed AUTH payload. This not-yet standardized
1098 extension requires the strongSwan vendor ID introduced above.
1100 - The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus
1101 allowing interoperability.
1107 - The IKEv1 pluto daemon can now use SQL-based address pools to deal out
1108 virtual IP addresses as a Mode Config server. The pool capability has been
1109 migrated from charon's sql plugin to a new attr-sql plugin which is loaded
1110 by libstrongswan and which can be used by both daemons either with a SQLite
1111 or MySQL database and the corresponding plugin.
1113 - Plugin names have been streamlined: EAP plugins now have a dash after eap
1114 (e.g. eap-sim), as it is used with the --enable-eap-sim ./configure option.
1115 Plugin configuration sections in strongswan.conf now use the same name as the
1116 plugin itself (i.e. with a dash). Make sure to update "load" directives and
1117 the affected plugin sections in existing strongswan.conf files.
1119 - The private/public key parsing and encoding has been split up into
1120 separate pkcs1, pgp, pem and dnskey plugins. The public key implementation
1121 plugins gmp, gcrypt and openssl can all make use of them.
1123 - The EAP-AKA plugin can use different backends for USIM/quintuplet
1124 calculations, very similar to the EAP-SIM plugin. The existing 3GPP2 software
1125 implementation has been migrated to a separate plugin.
1127 - The IKEv2 daemon charon gained basic PGP support. It can use locally installed
1128 peer certificates and can issue signatures based on RSA private keys.
1130 - The new 'ipsec pki' tool provides a set of commands to maintain a public
1131 key infrastructure. It currently supports operations to create RSA and ECDSA
1132 private/public keys, calculate fingerprints and issue or verify certificates.
1134 - Charon uses a monotonic time source for statistics and job queueing, behaving
1135 correctly if the system time changes (e.g. when using NTP).
1137 - In addition to time based rekeying, charon supports IPsec SA lifetimes based
1138 on processed volume or number of packets. They new ipsec.conf paramaters
1139 'lifetime' (an alias to 'keylife'), 'lifebytes' and 'lifepackets' handle
1140 SA timeouts, while the parameters 'margintime' (an alias to rekeymargin),
1141 'marginbytes' and 'marginpackets' trigger the rekeying before a SA expires.
1142 The existing parameter 'rekeyfuzz' affects all margins.
1144 - If no CA/Gateway certificate is specified in the NetworkManager plugin,
1145 charon uses a set of trusted root certificates preinstalled by distributions.
1146 The directory containing CA certificates can be specified using the
1147 --with-nm-ca-dir=path configure option.
1149 - Fixed the encoding of the Email relative distinguished name in left|rightid
1152 - Fixed the broken parsing of PKCS#7 wrapped certificates by the pluto daemon.
1154 - Fixed smartcard-based authentication in the pluto daemon which was broken by
1155 the ECDSA support introduced with the 4.3.2 release.
1157 - A patch contributed by Heiko Hund fixes mixed IPv6 in IPv4 and vice versa
1158 tunnels established with the IKEv1 pluto daemon.
1160 - The pluto daemon now uses the libstrongswan x509 plugin for certificates and
1161 CRls and the struct id type was replaced by identification_t used by charon
1162 and the libstrongswan library.
1168 - IKEv2 charon daemon ported to FreeBSD and Mac OS X. Installation details can
1169 be found on wiki.strongswan.org.
1171 - ipsec statusall shows the number of bytes transmitted and received over
1172 ESP connections configured by the IKEv2 charon daemon.
1174 - The IKEv2 charon daemon supports include files in ipsec.secrets.
1180 - The configuration option --enable-integrity-test plus the strongswan.conf
1181 option libstrongswan.integrity_test = yes activate integrity tests
1182 of the IKE daemons charon and pluto, libstrongswan and all loaded
1183 plugins. Thus dynamic library misconfigurations and non-malicious file
1184 manipulations can be reliably detected.
1186 - The new default setting libstrongswan.ecp_x_coordinate_only=yes allows
1187 IKEv1 interoperability with MS Windows using the ECP DH groups 19 and 20.
1189 - The IKEv1 pluto daemon now supports the AES-CCM and AES-GCM ESP
1190 authenticated encryption algorithms.
1192 - The IKEv1 pluto daemon now supports V4 OpenPGP keys.
1194 - The RDN parser vulnerability discovered by Orange Labs research team
1195 was not completely fixed in version 4.3.2. Some more modifications
1196 had to be applied to the asn1_length() function to make it robust.
1202 - The new gcrypt plugin provides symmetric cipher, hasher, RNG, Diffie-Hellman
1203 and RSA crypto primitives using the LGPL licensed GNU gcrypt library.
1205 - libstrongswan features an integrated crypto selftest framework for registered
1206 algorithms. The test-vector plugin provides a first set of test vectors and
1207 allows pluto and charon to rely on tested crypto algorithms.
1209 - pluto can now use all libstrongswan plugins with the exception of x509 and xcbc.
1210 Thanks to the openssl plugin, the ECP Diffie-Hellman groups 19, 20, 21, 25, and
1211 26 as well as ECDSA-256, ECDSA-384, and ECDSA-521 authentication can be used
1214 - Applying their fuzzing tool, the Orange Labs vulnerability research team found
1215 another two DoS vulnerabilities, one in the rather old ASN.1 parser of Relative
1216 Distinguished Names (RDNs) and a second one in the conversion of ASN.1 UTCTIME
1217 and GENERALIZEDTIME strings to a time_t value.
1223 - The nm plugin now passes DNS/NBNS server information to NetworkManager,
1224 allowing a gateway administrator to set DNS/NBNS configuration on clients
1227 - The nm plugin also accepts CA certificates for gateway authentication. If
1228 a CA certificate is configured, strongSwan uses the entered gateway address
1229 as its idenitity, requiring the gateways certificate to contain the same as
1230 subjectAltName. This allows a gateway administrator to deploy the same
1231 certificates to Windows 7 and NetworkManager clients.
1233 - The command ipsec purgeike deletes IKEv2 SAs that don't have a CHILD SA.
1234 The command ipsec down <conn>{n} deletes CHILD SA instance n of connection
1235 <conn> whereas ipsec down <conn>{*} deletes all CHILD SA instances.
1236 The command ipsec down <conn>[n] deletes IKE SA instance n of connection
1237 <conn> plus dependent CHILD SAs whereas ipsec down <conn>[*] deletes all
1238 IKE SA instances of connection <conn>.
1240 - Fixed a regression introduced in 4.3.0 where EAP authentication calculated
1241 the AUTH payload incorrectly. Further, the EAP-MSCHAPv2 MSK key derivation
1242 has been updated to be compatible with the Windows 7 Release Candidate.
1244 - Refactored installation of triggering policies. Routed policies are handled
1245 outside of IKE_SAs to keep them installed in any case. A tunnel gets
1246 established only once, even if initiation is delayed due network outages.
1248 - Improved the handling of multiple acquire signals triggered by the kernel.
1250 - Fixed two DoS vulnerabilities in the charon daemon that were discovered by
1251 fuzzing techniques: 1) Sending a malformed IKE_SA_INIT request leaved an
1252 incomplete state which caused a null pointer dereference if a subsequent
1253 CREATE_CHILD_SA request was sent. 2) Sending an IKE_AUTH request with either
1254 a missing TSi or TSr payload caused a null pointer derefence because the
1255 checks for TSi and TSr were interchanged. The IKEv2 fuzzer used was
1256 developed by the Orange Labs vulnerability research team. The tool was
1257 initially written by Gabriel Campana and is now maintained by Laurent Butti.
1259 - Added support for AES counter mode in ESP in IKEv2 using the proposal
1260 keywords aes128ctr, aes192ctr and aes256ctr.
1262 - Further progress in refactoring pluto: Use of the curl and ldap plugins
1263 for fetching crls and OCSP. Use of the random plugin to get keying material
1264 from /dev/random or /dev/urandom. Use of the openssl plugin as an alternative
1265 to the aes, des, sha1, sha2, and md5 plugins. The blowfish, twofish, and
1266 serpent encryption plugins are now optional and are not enabled by default.
1272 - Support for the IKEv2 Multiple Authentication Exchanges extension (RFC4739).
1273 Initiators and responders can use several authentication rounds (e.g. RSA
1274 followed by EAP) to authenticate. The new ipsec.conf leftauth/rightauth and
1275 leftauth2/rightauth2 parameters define own authentication rounds or setup
1276 constraints for the remote peer. See the ipsec.conf man page for more detials.
1278 - If glibc printf hooks (register_printf_function) are not available,
1279 strongSwan can use the vstr string library to run on non-glibc systems.
1281 - The IKEv2 charon daemon can now configure the ESP CAMELLIA-CBC cipher
1282 (esp=camellia128|192|256).
1284 - Refactored the pluto and scepclient code to use basic functions (memory
1285 allocation, leak detective, chunk handling, printf_hooks, strongswan.conf
1286 attributes, ASN.1 parser, etc.) from the libstrongswan library.
1288 - Up to two DNS and WINS servers to be sent via IKEv1 ModeConfig can be
1289 configured in the pluto section of strongswan.conf.
1295 - The new server-side EAP RADIUS plugin (--enable-eap-radius)
1296 relays EAP messages to and from a RADIUS server. Successfully
1297 tested with with a freeradius server using EAP-MD5 and EAP-SIM.
1299 - A vulnerability in the Dead Peer Detection (RFC 3706) code was found by
1300 Gerd v. Egidy <gerd.von.egidy@intra2net.com> of Intra2net AG affecting
1301 all Openswan and strongSwan releases. A malicious (or expired ISAKMP)
1302 R_U_THERE or R_U_THERE_ACK Dead Peer Detection packet can cause the
1303 pluto IKE daemon to crash and restart. No authentication or encryption
1304 is required to trigger this bug. One spoofed UDP packet can cause the
1305 pluto IKE daemon to restart and be unresponsive for a few seconds while
1306 restarting. This DPD null state vulnerability has been officially
1307 registered as CVE-2009-0790 and is fixed by this release.
1309 - ASN.1 to time_t conversion caused a time wrap-around for
1310 dates after Jan 18 03:14:07 UTC 2038 on 32-bit platforms.
1311 As a workaround such dates are set to the maximum representable
1312 time, i.e. Jan 19 03:14:07 UTC 2038.
1314 - Distinguished Names containing wildcards (*) are not sent in the
1315 IDr payload anymore.
1321 - Fixed a use-after-free bug in the DPD timeout section of the
1322 IKEv1 pluto daemon which sporadically caused a segfault.
1324 - Fixed a crash in the IKEv2 charon daemon occurring with
1325 mixed RAM-based and SQL-based virtual IP address pools.
1327 - Fixed ASN.1 parsing of algorithmIdentifier objects where the
1328 parameters field is optional.
1330 - Ported nm plugin to NetworkManager 7.1.
1336 - Support of the EAP-MSCHAPv2 protocol enabled by the option
1337 --enable-eap-mschapv2. Requires the MD4 hash algorithm enabled
1338 either by --enable-md4 or --enable-openssl.
1340 - Assignment of up to two DNS and up to two WINS servers to peers via
1341 the IKEv2 Configuration Payload (CP). The IPv4 or IPv6 nameserver
1342 addresses are defined in strongswan.conf.
1344 - The strongSwan applet for the Gnome NetworkManager is now built and
1345 distributed as a separate tarball under the name NetworkManager-strongswan.
1351 - Fixed ESP NULL encryption broken by the refactoring of keymat.c.
1352 Also introduced proper initialization and disposal of keying material.
1354 - Fixed the missing listing of connection definitions in ipsec statusall
1355 broken by an unfortunate local variable overload.
1361 - Several performance improvements to handle thousands of tunnels with almost
1362 linear upscaling. All relevant data structures have been replaced by faster
1363 counterparts with better lookup times.
1365 - Better parallelization to run charon on multiple cores. Due to improved
1366 ressource locking and other optimizations the daemon can take full
1367 advantage of 16 or even more cores.
1369 - The load-tester plugin can use a NULL Diffie-Hellman group and simulate
1370 unique identities and certificates by signing peer certificates using a CA
1373 - The redesigned stroke in-memory IP pool handles leases. The "ipsec leases"
1374 command queries assigned leases.
1376 - Added support for smartcards in charon by using the ENGINE API provided by
1377 OpenSSL, based on patches by Michael Roßberg.
1379 - The Padlock plugin supports the hardware RNG found on VIA CPUs to provide a
1380 reliable source of randomness.
1385 - Flexible configuration of logging subsystem allowing to log to multiple
1386 syslog facilities or to files using fine-grained log levels for each target.
1388 - Load testing plugin to do stress testing of the IKEv2 daemon against self
1389 or another host. Found and fixed issues during tests in the multi-threaded
1390 use of the OpenSSL plugin.
1392 - Added profiling code to synchronization primitives to find bottlenecks if
1393 running on multiple cores. Found and fixed an issue where parts of the
1394 Diffie-Hellman calculation acquired an exclusive lock. This greatly improves
1395 parallelization to multiple cores.
1397 - updown script invocation has been separated into a plugin of its own to
1398 further slim down the daemon core.
1400 - Separated IKE_SA/CHILD_SA key derivation process into a closed system,
1401 allowing future implementations to use a secured environment in e.g. kernel
1404 - The kernel interface of charon has been modularized. XFRM NETLINK (default)
1405 and PFKEY (--enable-kernel-pfkey) interface plugins for the native IPsec
1406 stack of the Linux 2.6 kernel as well as a PFKEY interface for the KLIPS
1407 IPsec stack (--enable-kernel-klips) are provided.
1409 - Basic Mobile IPv6 support has been introduced, securing Binding Update
1410 messages as well as tunneled traffic between Mobile Node and Home Agent.
1411 The installpolicy=no option allows peaceful cooperation with a dominant
1412 mip6d daemon and the new type=transport_proxy implements the special MIPv6
1413 IPsec transport proxy mode where the IKEv2 daemon uses the Care-of-Address
1414 but the IPsec SA is set up for the Home Address.
1416 - Implemented migration of Mobile IPv6 connections using the KMADDRESS
1417 field contained in XFRM_MSG_MIGRATE messages sent by the mip6d daemon
1418 via the Linux 2.6.28 (or appropriately patched) kernel.
1424 - IKEv2 charon daemon supports authentication based on raw public keys
1425 stored in the SQL database backend. The ipsec listpubkeys command
1426 lists the available raw public keys via the stroke interface.
1428 - Several MOBIKE improvements: Detect changes in NAT mappings in DPD exchanges,
1429 handle events if kernel detects NAT mapping changes in UDP-encapsulated
1430 ESP packets (requires kernel patch), reuse old addesses in MOBIKE updates as
1431 long as possible and other fixes.
1433 - Fixed a bug in addr_in_subnet() which caused insertion of wrong source
1434 routes for destination subnets having netwmasks not being a multiple of 8 bits.
1435 Thanks go to Wolfgang Steudel, TU Ilmenau for reporting this bug.
1441 - Fixed a Denial-of-Service vulnerability where an IKE_SA_INIT message with
1442 a KE payload containing zeroes only can cause a crash of the IKEv2 charon
1443 daemon due to a NULL pointer returned by the mpz_export() function of the
1444 GNU Multiprecision Library (GMP). Thanks go to Mu Dynamics Research Labs
1445 for making us aware of this problem.
1447 - The new agent plugin provides a private key implementation on top of an
1450 - The NetworkManager plugin has been extended to support certificate client
1451 authentication using RSA keys loaded from a file or using ssh-agent.
1453 - Daemon capability dropping has been ported to libcap and must be enabled
1454 explicitly --with-capabilities=libcap. Future version will support the
1455 newer libcap2 library.
1457 - ipsec listalgs lists the IKEv2 cryptografic algorithms registered with the
1458 charon keying daemon.
1464 - A NetworkManager plugin allows GUI-based configuration of road-warrior
1465 clients in a simple way. It features X509 based gateway authentication
1466 and EAP client authentication, tunnel setup/teardown and storing passwords
1467 in the Gnome Keyring.
1469 - A new EAP-GTC plugin implements draft-sheffer-ikev2-gtc-00.txt and allows
1470 username/password authentication against any PAM service on the gateway.
1471 The new EAP method interacts nicely with the NetworkManager plugin and allows
1472 client authentication against e.g. LDAP.
1474 - Improved support for the EAP-Identity method. The new ipsec.conf eap_identity
1475 parameter defines an additional identity to pass to the server in EAP
1478 - The "ipsec statusall" command now lists CA restrictions, EAP
1479 authentication types and EAP identities.
1481 - Fixed two multithreading deadlocks occurring when starting up
1482 several hundred tunnels concurrently.
1484 - Fixed the --enable-integrity-test configure option which
1485 computes a SHA-1 checksum over the libstrongswan library.
1491 - Consistent logging of IKE and CHILD SAs at the audit (AUD) level.
1493 - Improved the performance of the SQL-based virtual IP address pool
1494 by introducing an additional addresses table. The leases table
1495 storing only history information has become optional and can be
1496 disabled by setting charon.plugins.sql.lease_history = no in
1499 - The XFRM_STATE_AF_UNSPEC flag added to xfrm.h allows IPv4-over-IPv6
1500 and IPv6-over-IPv4 tunnels with the 2.6.26 and later Linux kernels.
1502 - management of different virtual IP pools for different
1503 network interfaces have become possible.
1505 - fixed a bug which prevented the assignment of more than 256
1506 virtual IP addresses from a pool managed by an sql database.
1508 - fixed a bug which did not delete own IPCOMP SAs in the kernel.
1514 - Added statistics functions to ipsec pool --status and ipsec pool --leases
1515 and input validation checks to various ipsec pool commands.
1517 - ipsec statusall now lists all loaded charon plugins and displays
1518 the negotiated IKEv2 cipher suite proposals.
1520 - The openssl plugin supports the elliptic curve Diffie-Hellman groups
1521 19, 20, 21, 25, and 26.
1523 - The openssl plugin supports ECDSA authentication using elliptic curve
1526 - Fixed a bug in stroke which caused multiple charon threads to close
1527 the file descriptors during packet transfers over the stroke socket.
1529 - ESP sequence numbers are now migrated in IPsec SA updates handled by
1530 MOBIKE. Works only with Linux kernels >= 2.6.17.
1536 - Fixed the strongswan.conf path configuration problem that occurred when
1537 --sysconfig was not set explicitly in ./configure.
1539 - Fixed a number of minor bugs that where discovered during the 4th
1540 IKEv2 interoperability workshop in San Antonio, TX.
1546 - Plugins for libstrongswan and charon can optionally be loaded according
1547 to a configuration in strongswan.conf. Most components provide a
1548 "load = " option followed by a space separated list of plugins to load.
1549 This allows e.g. the fallback from a hardware crypto accelerator to
1550 to software-based crypto plugins.
1552 - Charons SQL plugin has been extended by a virtual IP address pool.
1553 Configurations with a rightsourceip=%poolname setting query a SQLite or
1554 MySQL database for leases. The "ipsec pool" command helps in administrating
1555 the pool database. See ipsec pool --help for the available options
1557 - The Authenticated Encryption Algorithms AES-CCM-8/12/16 and AES-GCM-8/12/16
1558 for ESP are now supported starting with the Linux 2.6.25 kernel. The
1559 syntax is e.g. esp=aes128ccm12 or esp=aes256gcm16.
1565 - Support for "Hash and URL" encoded certificate payloads has been implemented
1566 in the IKEv2 daemon charon. Using the "certuribase" option of a CA section
1567 allows to assign a base URL to all certificates issued by the specified CA.
1568 The final URL is then built by concatenating that base and the hex encoded
1569 SHA1 hash of the DER encoded certificate. Note that this feature is disabled
1570 by default and must be enabled using the option "charon.hash_and_url".
1572 - The IKEv2 daemon charon now supports the "uniqueids" option to close multiple
1573 IKE_SAs with the same peer. The option value "keep" prefers existing
1574 connection setups over new ones, where the value "replace" replaces existing
1577 - The crypto factory in libstrongswan additionally supports random number
1578 generators, plugins may provide other sources of randomness. The default
1579 plugin reads raw random data from /dev/(u)random.
1581 - Extended the credential framework by a caching option to allow plugins
1582 persistent caching of fetched credentials. The "cachecrl" option has been
1585 - The new trustchain verification introduced in 4.2.0 has been parallelized.
1586 Threads fetching CRL or OCSP information no longer block other threads.
1588 - A new IKEv2 configuration attribute framework has been introduced allowing
1589 plugins to provide virtual IP addresses, and in the future, other
1590 configuration attribute services (e.g. DNS/WINS servers).
1592 - The stroke plugin has been extended to provide virtual IP addresses from
1593 a pool defined in ipsec.conf. The "rightsourceip" parameter now accepts
1594 address pools in CIDR notation (e.g. 10.1.1.0/24). The parameter also accepts
1595 the value "%poolname", where "poolname" identifies a pool provided by a
1598 - Fixed compilation on uClibc and a couple of other minor bugs.
1600 - Set DPD defaults in ipsec starter to dpd_delay=30s and dpd_timeout=150s.
1602 - The IKEv1 pluto daemon now supports the ESP encryption algorithm CAMELLIA
1603 with key lengths of 128, 192, and 256 bits, as well as the authentication
1604 algorithm AES_XCBC_MAC. Configuration example: esp=camellia192-aesxcbc.
1610 - libstrongswan has been modularized to attach crypto algorithms,
1611 credential implementations (keys, certificates) and fetchers dynamically
1612 through plugins. Existing code has been ported to plugins:
1613 - RSA/Diffie-Hellman implementation using the GNU Multi Precision library
1614 - X509 certificate system supporting CRLs, OCSP and attribute certificates
1615 - Multiple plugins providing crypto algorithms in software
1616 - CURL and OpenLDAP fetcher
1618 - libstrongswan gained a relational database API which uses pluggable database
1619 providers. Plugins for MySQL and SQLite are available.
1621 - The IKEv2 keying daemon charon is more extensible. Generic plugins may provide
1622 connection configuration, credentials and EAP methods or control the daemon.
1623 Existing code has been ported to plugins:
1624 - EAP-AKA, EAP-SIM, EAP-MD5 and EAP-Identity
1625 - stroke configuration, credential and control (compatible to pluto)
1626 - XML bases management protocol to control and query the daemon
1627 The following new plugins are available:
1628 - An experimental SQL configuration, credential and logging plugin on
1629 top of either MySQL or SQLite
1630 - A unit testing plugin to run tests at daemon startup
1632 - The authentication and credential framework in charon has been heavily
1633 refactored to support modular credential providers, proper
1634 CERTREQ/CERT payload exchanges and extensible authorization rules.
1636 - The framework of strongSwan Manager has envolved to the web application
1637 framework libfast (FastCGI Application Server w/ Templates) and is usable
1638 by other applications.
1644 - IKE rekeying in NAT situations did not inherit the NAT conditions
1645 to the rekeyed IKE_SA so that the UDP encapsulation was lost with
1646 the next CHILD_SA rekeying.
1648 - Wrong type definition of the next_payload variable in id_payload.c
1649 caused an INVALID_SYNTAX error on PowerPC platforms.
1651 - Implemented IKEv2 EAP-SIM server and client test modules that use
1652 triplets stored in a file. For details on the configuration see
1653 the scenario 'ikev2/rw-eap-sim-rsa'.
1659 - Fixed error in the ordering of the certinfo_t records in the ocsp cache that
1660 caused multiple entries of the same serial number to be created.
1662 - Implementation of a simple EAP-MD5 module which provides CHAP
1663 authentication. This may be interesting in conjunction with certificate
1664 based server authentication, as weak passwords can't be brute forced
1665 (in contradiction to traditional IKEv2 PSK).
1667 - A complete software based implementation of EAP-AKA, using algorithms
1668 specified in 3GPP2 (S.S0055). This implementation does not use an USIM,
1669 but reads the secrets from ipsec.secrets. Make sure to read eap_aka.h
1672 - Support for vendor specific EAP methods using Expanded EAP types. The
1673 interface to EAP modules has been slightly changed, so make sure to
1674 check the changes if you're already rolling your own modules.
1680 - The default _updown script now dynamically inserts and removes ip6tables
1681 firewall rules if leftfirewall=yes is set in IPv6 connections. New IPv6
1682 net-net and roadwarrior (PSK/RSA) scenarios for both IKEv1 and IKEV2 were
1685 - Implemented RFC4478 repeated authentication to force EAP/Virtual-IP clients
1686 to reestablish an IKE_SA within a given timeframe.
1688 - strongSwan Manager supports configuration listing, initiation and termination
1689 of IKE and CHILD_SAs.
1691 - Fixes and improvements to multithreading code.
1693 - IKEv2 plugins have been renamed to libcharon-* to avoid naming conflicts.
1694 Make sure to remove the old plugins in $libexecdir/ipsec, otherwise they get
1701 - Removed recursive pthread mutexes since uClibc doesn't support them.
1707 - In NAT traversal situations and multiple queued Quick Modes,
1708 those pending connections inserted by auto=start after the
1709 port floating from 500 to 4500 were erronously deleted.
1711 - Added a "forceencaps" connection parameter to enforce UDP encapsulation
1712 to surmount restrictive firewalls. NAT detection payloads are faked to
1713 simulate a NAT situation and trick the other peer into NAT mode (IKEv2 only).
1715 - Preview of strongSwan Manager, a web based configuration and monitoring
1716 application. It uses a new XML control interface to query the IKEv2 daemon
1717 (see http://wiki.strongswan.org/wiki/Manager).
1719 - Experimental SQLite configuration backend which will provide the configuration
1720 interface for strongSwan Manager in future releases.
1722 - Further improvements to MOBIKE support.
1728 - Since some third party IKEv2 implementations run into
1729 problems with strongSwan announcing MOBIKE capability per
1730 default, MOBIKE can be disabled on a per-connection-basis
1731 using the mobike=no option. Whereas mobike=no disables the
1732 sending of the MOBIKE_SUPPORTED notification and the floating
1733 to UDP port 4500 with the IKE_AUTH request even if no NAT
1734 situation has been detected, strongSwan will still support
1735 MOBIKE acting as a responder.
1737 - the default ipsec routing table plus its corresponding priority
1738 used for inserting source routes has been changed from 100 to 220.
1739 It can be configured using the --with-ipsec-routing-table and
1740 --with-ipsec-routing-table-prio options.
1742 - the --enable-integrity-test configure option tests the
1743 integrity of the libstrongswan crypto code during the charon
1746 - the --disable-xauth-vid configure option disables the sending
1747 of the XAUTH vendor ID. This can be used as a workaround when
1748 interoperating with some Windows VPN clients that get into
1749 trouble upon reception of an XAUTH VID without eXtended
1750 AUTHentication having been configured.
1752 - ipsec stroke now supports the rereadsecrets, rereadaacerts,
1753 rereadacerts, and listacerts options.
1759 - If a DNS lookup failure occurs when resolving right=%<FQDN>
1760 or right=<FQDN> combined with rightallowany=yes then the
1761 connection is not updated by ipsec starter thus preventing
1762 the disruption of an active IPsec connection. Only if the DNS
1763 lookup successfully returns with a changed IP address the
1764 corresponding connection definition is updated.
1766 - Routes installed by the keying daemons are now in a separate
1767 routing table with the ID 100 to avoid conflicts with the main
1768 table. Route lookup for IKEv2 traffic is done in userspace to ignore
1769 routes installed for IPsec, as IKE traffic shouldn't get encapsulated.
1775 - The pluto IKEv1 daemon now exhibits the same behaviour as its
1776 IKEv2 companion charon by inserting an explicit route via the
1777 _updown script only if a sourceip exists. This is admissible
1778 since routing through the IPsec tunnel is handled automatically
1779 by NETKEY's IPsec policies. As a consequence the left|rightnexthop
1780 parameter is not required any more.
1782 - The new IKEv1 parameter right|leftallowany parameters helps to handle
1783 the case where both peers possess dynamic IP addresses that are
1784 usually resolved using DynDNS or a similar service. The configuration
1789 can be used by the initiator to start up a connection to a peer
1790 by resolving peer.foo.bar into the currently allocated IP address.
1791 Thanks to the rightallowany flag the connection behaves later on
1796 so that the peer can rekey the connection as an initiator when his
1797 IP address changes. An alternative notation is
1801 which will implicitly set rightallowany=yes.
1803 - ipsec starter now fails more gracefully in the presence of parsing
1804 errors. Flawed ca and conn section are discarded and pluto is started
1805 if non-fatal errors only were encountered. If right=%peer.foo.bar
1806 cannot be resolved by DNS then right=%any will be used so that passive
1807 connections as a responder are still possible.
1809 - The new pkcs11initargs parameter that can be placed in the
1810 setup config section of /etc/ipsec.conf allows the definition
1811 of an argument string that is used with the PKCS#11 C_Initialize()
1812 function. This non-standard feature is required by the NSS softoken
1813 library. This patch was contributed by Robert Varga.
1815 - Fixed a bug in ipsec starter introduced by strongswan-2.8.5
1816 which caused a segmentation fault in the presence of unknown
1817 or misspelt keywords in ipsec.conf. This bug fix was contributed
1820 - Partial support for MOBIKE in IKEv2. The initiator acts on interface/
1821 address configuration changes and updates IKE and IPsec SAs dynamically.
1827 - IKEv2 peer configuration selection now can be based on a given
1828 certification authority using the rightca= statement.
1830 - IKEv2 authentication based on RSA signatures now can handle multiple
1831 certificates issued for a given peer ID. This allows a smooth transition
1832 in the case of a peer certificate renewal.
1834 - IKEv2: Support for requesting a specific virtual IP using leftsourceip on the
1835 client and returning requested virtual IPs using rightsourceip=%config
1836 on the server. If the server does not support configuration payloads, the
1837 client enforces its leftsourceip parameter.
1839 - The ./configure options --with-uid/--with-gid allow pluto and charon
1840 to drop their privileges to a minimum and change to an other UID/GID. This
1841 improves the systems security, as a possible intruder may only get the
1842 CAP_NET_ADMIN capability.
1844 - Further modularization of charon: Pluggable control interface and
1845 configuration backend modules provide extensibility. The control interface
1846 for stroke is included, and further interfaces using DBUS (NetworkManager)
1847 or XML are on the way. A backend for storing configurations in the daemon
1848 is provided and more advanced backends (using e.g. a database) are trivial
1851 - Fixed a compilation failure in libfreeswan occurring with Linux kernel
1858 - Support for an additional Diffie-Hellman exchange when creating/rekeying
1859 a CHILD_SA in IKEv2 (PFS). PFS is enabled when the proposal contains a
1860 DH group (e.g. "esp=aes128-sha1-modp1536"). Further, DH group negotiation
1861 is implemented properly for rekeying.
1863 - Support for the AES-XCBC-96 MAC algorithm for IPsec SAs when using IKEv2
1864 (requires linux >= 2.6.20). It is enabled using e.g. "esp=aes256-aesxcbc".
1866 - Working IPv4-in-IPv6 and IPv6-in-IPv4 tunnels for linux >= 2.6.21.
1868 - Added support for EAP modules which do not establish an MSK.
1870 - Removed the dependencies from the /usr/include/linux/ headers by
1871 including xfrm.h, ipsec.h, and pfkeyv2.h in the distribution.
1873 - crlNumber is now listed by ipsec listcrls
1875 - The xauth_modules.verify_secret() function now passes the
1882 - Server side cookie support. If to may IKE_SAs are in CONNECTING state,
1883 cookies are enabled and protect against DoS attacks with faked source
1884 addresses. Number of IKE_SAs in CONNECTING state is also limited per
1885 peer address to avoid resource exhaustion. IKE_SA_INIT messages are
1886 compared to properly detect retransmissions and incoming retransmits are
1887 detected even if the IKE_SA is blocked (e.g. doing OCSP fetches).
1889 - The IKEv2 daemon charon now supports dynamic http- and ldap-based CRL
1890 fetching enabled by crlcheckinterval > 0 and caching fetched CRLs
1891 enabled by cachecrls=yes.
1893 - Added the configuration options --enable-nat-transport which enables
1894 the potentially insecure NAT traversal for IPsec transport mode and
1895 --disable-vendor-id which disables the sending of the strongSwan
1898 - Fixed a long-standing bug in the pluto IKEv1 daemon which caused
1899 a segmentation fault if a malformed payload was detected in the
1900 IKE MR2 message and pluto tried to send an encrypted notification
1903 - Added the NATT_IETF_02_N Vendor ID in order to support IKEv1 connections
1904 with Windows 2003 Server which uses a wrong VID hash.
1910 - Support of SHA2_384 hash function for protecting IKEv1
1911 negotiations and support of SHA2 signatures in X.509 certificates.
1913 - Fixed a serious bug in the computation of the SHA2-512 HMAC
1914 function. Introduced automatic self-test of all IKEv1 hash
1915 and hmac functions during pluto startup. Failure of a self-test
1916 currently issues a warning only but does not exit pluto [yet].
1918 - Support for SHA2-256/384/512 PRF and HMAC functions in IKEv2.
1920 - Full support of CA information sections. ipsec listcainfos
1921 now shows all collected crlDistributionPoints and OCSP
1924 - Support of the Online Certificate Status Protocol (OCSP) for IKEv2.
1925 This feature requires the HTTP fetching capabilities of the libcurl
1926 library which must be enabled by setting the --enable-http configure
1929 - Refactored core of the IKEv2 message processing code, allowing better
1930 code reuse and separation.
1932 - Virtual IP support in IKEv2 using INTERNAL_IP4/6_ADDRESS configuration
1933 payload. Additionally, the INTERNAL_IP4/6_DNS attribute is interpreted
1934 by the requestor and installed in a resolv.conf file.
1936 - The IKEv2 daemon charon installs a route for each IPsec policy to use
1937 the correct source address even if an application does not explicitly
1940 - Integrated the EAP framework into charon which loads pluggable EAP library
1941 modules. The ipsec.conf parameter authby=eap initiates EAP authentication
1942 on the client side, while the "eap" parameter on the server side defines
1943 the EAP method to use for client authentication.
1944 A generic client side EAP-Identity module and an EAP-SIM authentication
1945 module using a third party card reader implementation are included.
1947 - Added client side support for cookies.
1949 - Integrated the fixes done at the IKEv2 interoperability bakeoff, including
1950 strict payload order, correct INVALID_KE_PAYLOAD rejection and other minor
1951 fixes to enhance interoperability with other implementations.
1957 - strongSwan now interoperates with the NCP Secure Entry Client,
1958 the Shrew Soft VPN Client, and the Cisco VPN client, doing both
1959 XAUTH and Mode Config.
1961 - UNITY attributes are now recognized and UNITY_BANNER is set
1962 to a default string.
1968 - IKEv1: Support for extended authentication (XAUTH) in combination
1969 with ISAKMP Main Mode RSA or PSK authentication. Both client and
1970 server side were implemented. Handling of user credentials can
1971 be done by a run-time loadable XAUTH module. By default user
1972 credentials are stored in ipsec.secrets.
1974 - IKEv2: Support for reauthentication when rekeying
1976 - IKEv2: Support for transport mode
1978 - fixed a lot of bugs related to byte order
1980 - various other bugfixes
1986 - IKEv1: Implementation of ModeConfig push mode via the new connection
1987 keyword modeconfig=push allows interoperability with Cisco VPN gateways.
1989 - IKEv1: The command ipsec statusall now shows "DPD active" for all
1990 ISAKMP SAs that are under active Dead Peer Detection control.
1992 - IKEv2: Charon's logging and debugging framework has been completely rewritten.
1993 Instead of logger, special printf() functions are used to directly
1994 print objects like hosts (%H) identifications (%D), certificates (%Q),
1995 etc. The number of debugging levels have been reduced to:
1997 0 (audit), 1 (control), 2 (controlmore), 3 (raw), 4 (private)
1999 The debugging levels can either be specified statically in ipsec.conf as
2002 charondebug="lib 1, cfg 3, net 2"
2004 or changed at runtime via stroke as
2006 ipsec stroke loglevel cfg 2
2012 - Implemented full support for IPv6-in-IPv6 tunnels.
2014 - Added configuration options for dead peer detection in IKEv2. dpd_action
2015 types "clear", "hold" and "restart" are supported. The dpd_timeout
2016 value is not used, as the normal retransmission policy applies to
2017 detect dead peers. The dpd_delay parameter enables sending of empty
2018 informational message to detect dead peers in case of inactivity.
2020 - Added support for preshared keys in IKEv2. PSK keys configured in
2021 ipsec.secrets are loaded. The authby parameter specifies the authentication
2022 method to authentificate ourself, the other peer may use PSK or RSA.
2024 - Changed retransmission policy to respect the keyingtries parameter.
2026 - Added private key decryption. PEM keys encrypted with AES-128/192/256
2027 or 3DES are supported.
2029 - Implemented DES/3DES algorithms in libstrongswan. 3DES can be used to
2030 encrypt IKE traffic.
2032 - Implemented SHA-256/384/512 in libstrongswan, allows usage of certificates
2033 signed with such a hash algorithm.
2035 - Added initial support for updown scripts. The actions up-host/client and
2036 down-host/client are executed. The leftfirewall=yes parameter
2037 uses the default updown script to insert dynamic firewall rules, a custom
2038 updown script may be specified with the leftupdown parameter.
2044 - Added support for the auto=route ipsec.conf parameter and the
2045 ipsec route/unroute commands for IKEv2. This allows to set up IKE_SAs and
2046 CHILD_SAs dynamically on demand when traffic is detected by the
2049 - Added support for rekeying IKE_SAs in IKEv2 using the ikelifetime parameter.
2050 As specified in IKEv2, no reauthentication is done (unlike in IKEv1), only
2051 new keys are generated using perfect forward secrecy. An optional flag
2052 which enforces reauthentication will be implemented later.
2054 - "sha" and "sha1" are now treated as synonyms in the ike= and esp=
2055 algorithm configuration statements.
2061 - Full X.509 certificate trust chain verification has been implemented.
2062 End entity certificates can be exchanged via CERT payloads. The current
2063 default is leftsendcert=always, since CERTREQ payloads are not supported
2064 yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls.
2066 - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2
2067 would offer more possibilities for traffic selection, but the Linux kernel
2068 currently does not support it. That's why we stick with these simple
2069 ipsec.conf rules for now.
2071 - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no
2072 IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear,
2075 - Initial NAT traversal support in IKEv2. Charon includes NAT detection
2076 notify payloads to detect NAT routers between the peers. It switches
2077 to port 4500, uses UDP encapsulated ESP packets, handles peer address
2078 changes gracefully and sends keep alive message periodically.
2080 - Reimplemented IKE_SA state machine for charon, which allows simultaneous
2081 rekeying, more shared code, cleaner design, proper retransmission
2082 and a more extensible code base.
2084 - The mixed PSK/RSA roadwarrior detection capability introduced by the
2085 strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal
2086 payloads by the responder right before any defined IKE Main Mode state had
2087 been established. Although any form of bad proposal syntax was being correctly
2088 detected by the payload parser, the subsequent error handler didn't check
2089 the state pointer before logging current state information, causing an
2090 immediate crash of the pluto keying daemon due to a NULL pointer.
2096 - Added algorithm selection to charon: New default algorithms for
2097 ike=aes128-sha-modp2048, as both daemons support it. The default
2098 for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles
2099 the ike/esp parameter the same way as pluto. As this syntax does
2100 not allow specification of a pseudo random function, the same
2101 algorithm as for integrity is used (currently sha/md5). Supported
2103 Encryption: aes128, aes192, aes256
2104 Integrity/PRF: md5, sha (using hmac)
2105 DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192
2107 Encryption: aes128, aes192, aes256, 3des, blowfish128,
2108 blowfish192, blowfish256
2109 Integrity: md5, sha1
2110 More IKE encryption algorithms will come after porting libcrypto into
2113 - initial support for rekeying CHILD_SAs using IKEv2. Currently no
2114 perfect forward secrecy is used. The rekeying parameters rekey,
2115 rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported
2116 when using IKEv2. WARNING: charon currently is unable to handle
2117 simultaneous rekeying. To avoid such a situation, use a large
2118 rekeyfuzz, or even better, set rekey=no on one peer.
2120 - support for host2host, net2net, host2net (roadwarrior) tunnels
2121 using predefined RSA certificates (see uml scenarios for
2122 configuration examples).
2124 - new build environment featuring autotools. Features such
2125 as HTTP, LDAP and smartcard support may be enabled using
2126 the ./configure script. Changing install directories
2127 is possible, too. See ./configure --help for more details.
2129 - better integration of charon with ipsec starter, which allows
2130 (almost) transparent operation with both daemons. charon
2131 handles ipsec commands up, down, status, statusall, listall,
2132 listcerts and allows proper load, reload and delete of connections
2139 - initial support of the IKEv2 protocol. Connections in
2140 ipsec.conf designated by keyexchange=ikev2 are negotiated
2141 by the new IKEv2 charon keying daemon whereas those marked
2142 by keyexchange=ikev1 or the default keyexchange=ike are
2143 handled thy the IKEv1 pluto keying daemon. Currently only
2144 a limited subset of functions are available with IKEv2
2145 (Default AES encryption, authentication based on locally
2146 imported X.509 certificates, unencrypted private RSA keys
2147 in PKCS#1 file format, limited functionality of the ipsec
2154 - the dynamic iptables rules from the _updown_x509 template
2155 for KLIPS and the _updown_policy template for NETKEY have
2156 been merged into the default _updown script. The existing
2157 left|rightfirewall keyword causes the automatic insertion
2158 and deletion of ACCEPT rules for tunneled traffic upon
2159 the successful setup and teardown of an IPsec SA, respectively.
2160 left|rightfirwall can be used with KLIPS under any Linux 2.4
2161 kernel or with NETKEY under a Linux kernel version >= 2.6.16
2162 in conjunction with iptables >= 1.3.5. For NETKEY under a Linux
2163 kernel version < 2.6.16 which does not support IPsec policy
2164 matching yet, please continue to use a copy of the _updown_espmark
2165 template loaded via the left|rightupdown keyword.
2167 - a new left|righthostaccess keyword has been introduced which
2168 can be used in conjunction with left|rightfirewall and the
2169 default _updown script. By default leftfirewall=yes inserts
2170 a bi-directional iptables FORWARD rule for a local client network
2171 with a netmask different from 255.255.255.255 (single host).
2172 This does not allow to access the VPN gateway host via its
2173 internal network interface which is part of the client subnet
2174 because an iptables INPUT and OUTPUT rule would be required.
2175 lefthostaccess=yes will cause this additional ACCEPT rules to
2178 - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal
2179 payload is preparsed in order to find out whether the roadwarrior
2180 requests PSK or RSA so that a matching connection candidate can
2187 - the new _updown_policy template allows ipsec policy based
2188 iptables firewall rules. Required are iptables version
2189 >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes
2190 the _updown_espmark template, so that no INPUT mangle rules
2191 are required any more.
2193 - added support of DPD restart mode
2195 - ipsec starter now allows the use of wildcards in include
2196 statements as e.g. in "include /etc/my_ipsec/*.conf".
2197 Patch courtesy of Matthias Haas.
2199 - the Netscape OID 'employeeNumber' is now recognized and can be
2200 used as a Relative Distinguished Name in certificates.
2206 - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec
2207 command and not of ipsec setup any more.
2209 - ipsec starter now supports AH authentication in conjunction with
2210 ESP encryption. AH authentication is configured in ipsec.conf
2211 via the auth=ah parameter.
2213 - The command ipsec scencrypt|scdecrypt <args> is now an alias for
2214 ipsec whack --scencrypt|scdecrypt <args>.
2216 - get_sa_info() now determines for the native netkey IPsec stack
2217 the exact time of the last use of an active eroute. This information
2218 is used by the Dead Peer Detection algorithm and is also displayed by
2219 the ipsec status command.
2225 - running under the native Linux 2.6 IPsec stack, the function
2226 get_sa_info() is called by ipsec auto --status to display the current
2227 number of transmitted bytes per IPsec SA.
2229 - get_sa_info() is also used by the Dead Peer Detection process to detect
2230 recent ESP activity. If ESP traffic was received from the peer within
2231 the last dpd_delay interval then no R_Y_THERE notification must be sent.
2233 - strongSwan now supports the Relative Distinguished Name "unstructuredName"
2234 in ID_DER_ASN1_DN identities. The following notations are possible:
2236 rightid="unstructuredName=John Doe"
2237 rightid="UN=John Doe"
2239 - fixed a long-standing bug which caused PSK-based roadwarrior connections
2240 to segfault in the function id.c:same_id() called by keys.c:get_secret()
2241 if an FQDN, USER_FQDN, or Key ID was defined, as in the following example.
2248 - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall).
2250 - ipsec starter didn't set host_addr and client.addr ports in whack msg.
2252 - in order to guarantee backwards-compatibility with the script-based
2253 auto function (e.g. auto --replace), the ipsec starter scripts stores
2254 the defaultroute information in the temporary file /var/run/ipsec.info.
2256 - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH
2257 Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config
2260 - the ipsec starter now also recognizes the parameters authby=never and
2261 type=passthrough|pass|drop|reject.
2267 - ipsec starter now supports the also parameter which allows
2268 a modular structure of the connection definitions. Thus
2269 "ipsec start" is now ready to replace "ipsec setup".
2275 - Mathieu Lafon's popular ipsec starter tool has been added to the
2276 strongSwan distribution. Many thanks go to Stephan Scholz from astaro
2277 for his integration work. ipsec starter is a C program which is going
2278 to replace the various shell and awk starter scripts (setup, _plutoload,
2279 _plutostart, _realsetup, _startklips, _confread, and auto). Since
2280 ipsec.conf is now parsed only once, the starting of multiple tunnels is
2281 accelerated tremedously.
2283 - Added support of %defaultroute to the ipsec starter. If the IP address
2284 changes, a HUP signal to the ipsec starter will automatically
2285 reload pluto's connections.
2287 - moved most compile time configurations from pluto/Makefile to
2288 Makefile.inc by defining the options USE_LIBCURL, USE_LDAP,
2289 USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE.
2291 - removed the ipsec verify and ipsec newhostkey commands
2293 - fixed some 64-bit issues in formatted print statements
2295 - The scepclient functionality implementing the Simple Certificate
2296 Enrollment Protocol (SCEP) is nearly complete but hasn't been
2303 - CA certicates are now automatically loaded from a smartcard
2304 or USB crypto token and appear in the ipsec auto --listcacerts
2311 - when using "ipsec whack --scencrypt <data>" with a PKCS#11
2312 library that does not support the C_Encrypt() Cryptoki
2313 function (e.g. OpenSC), the RSA encryption is done in
2314 software using the public key fetched from the smartcard.
2316 - The scepclient function now allows to define the
2317 validity of a self-signed certificate using the --days,
2318 --startdate, and --enddate options. The default validity
2319 has been changed from one year to five years.
2325 - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11
2326 interface to other applications for RSA encryption and decryption
2327 via the whack interface. Notation:
2329 ipsec whack --scencrypt <data>
2330 [--inbase 16|hex|64|base64|256|text|ascii]
2331 [--outbase 16|hex|64|base64|256|text|ascii]
2334 ipsec whack --scdecrypt <data>
2335 [--inbase 16|hex|64|base64|256|text|ascii]
2336 [--outbase 16|hex|64|base64|256|text|ascii]
2339 The default setting for inbase and outbase is hex.
2341 The new proxy interface can be used for securing symmetric
2342 encryption keys required by the cryptoloop or dm-crypt
2343 disk encryption schemes, especially in the case when
2344 pkcs11keepstate=yes causes pluto to lock the pkcs11 slot
2347 - if the file /etc/ipsec.secrets is lacking during the startup of
2348 pluto then the root-readable file /etc/ipsec.d/private/myKey.der
2349 containing a 2048 bit RSA private key and a matching self-signed
2350 certificate stored in the file /etc/ipsec.d/certs/selfCert.der
2351 is automatically generated by calling the function
2353 ipsec scepclient --out pkcs1 --out cert-self
2355 scepclient was written by Jan Hutter and Martin Willi, students
2356 at the University of Applied Sciences in Rapperswil, Switzerland.
2362 - the current extension of the PKCS#7 framework introduced
2363 a parsing error in PKCS#7 wrapped X.509 certificates that are
2364 e.g. transmitted by Windows XP when multi-level CAs are used.
2365 the parsing syntax has been fixed.
2367 - added a patch by Gerald Richter which tolerates multiple occurrences
2368 of the ipsec0 interface when using KLIPS.
2374 - with gawk-3.1.4 the word "default2 has become a protected
2375 keyword for use in switch statements and cannot be used any
2376 more in the strongSwan scripts. This problem has been
2377 solved by renaming "default" to "defaults" and "setdefault"
2378 in the scripts _confread and auto, respectively.
2380 - introduced the parameter leftsendcert with the values
2382 always|yes (the default, always send a cert)
2383 ifasked (send the cert only upon a cert request)
2384 never|no (never send a cert, used for raw RSA keys and
2387 - fixed the initialization of the ESP key length to a default of
2388 128 bits in the case that the peer does not send a key length
2389 attribute for AES encryption.
2391 - applied Herbert Xu's uniqueIDs patch
2393 - applied Herbert Xu's CLOEXEC patches
2399 - CRLs can now be cached also in the case when the issuer's
2400 certificate does not contain a subjectKeyIdentifier field.
2401 In that case the subjectKeyIdentifier is computed by pluto as the
2402 160 bit SHA-1 hash of the issuer's public key in compliance
2403 with section 4.2.1.2 of RFC 3280.
2405 - Fixed a bug introduced by strongswan-2.5.1 which eliminated
2406 not only multiple Quick Modes of a given connection but also
2407 multiple connections between two security gateways.
2413 - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute
2414 installed either by setting auto=route in ipsec.conf or by
2415 a connection put into hold, generates an XFRM_AQUIRE event
2416 for each packet that wants to use the not-yet exisiting
2417 tunnel. Up to now each XFRM_AQUIRE event led to an entry in
2418 the Quick Mode queue, causing multiple IPsec SA to be
2419 established in rapid succession. Starting with strongswan-2.5.1
2420 only a single IPsec SA is established per host-pair connection.
2422 - Right after loading the PKCS#11 module, all smartcard slots are
2423 searched for certificates. The result can be viewed using
2426 ipsec auto --listcards
2428 The certificate objects found in the slots are numbered
2429 starting with #1, #2, etc. This position number can be used to address
2430 certificates (leftcert=%smartcard) and keys (: PIN %smartcard)
2431 in ipsec.conf and ipsec.secrets, respectively:
2433 %smartcard (selects object #1)
2434 %smartcard#1 (selects object #1)
2435 %smartcard#3 (selects object #3)
2437 As an alternative the existing retrieval scheme can be used:
2439 %smartcard:45 (selects object with id=45)
2440 %smartcard0 (selects first object in slot 0)
2441 %smartcard4:45 (selects object in slot 4 with id=45)
2443 - Depending on the settings of CKA_SIGN and CKA_DECRYPT
2444 private key flags either C_Sign() or C_Decrypt() is used
2445 to generate a signature.
2447 - The output buffer length parameter siglen in C_Sign()
2448 is now initialized to the actual size of the output
2449 buffer prior to the function call. This fixes the
2450 CKR_BUFFER_TOO_SMALL error that could occur when using
2451 the OpenSC PKCS#11 module.
2453 - Changed the initialization of the PKCS#11 CK_MECHANISM in
2454 C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }.
2456 - Refactored the RSA public/private key code and transferred it
2457 from keys.c to the new pkcs1.c file as a preparatory step
2458 towards the release of the SCEP client.
2464 - The loading of a PKCS#11 smartcard library module during
2465 runtime does not require OpenSC library functions any more
2466 because the corresponding code has been integrated into
2467 smartcard.c. Also the RSAREF pkcs11 header files have been
2468 included in a newly created pluto/rsaref directory so that
2469 no external include path has to be defined any longer.
2471 - A long-awaited feature has been implemented at last:
2472 The local caching of CRLs fetched via HTTP or LDAP, activated
2473 by the parameter cachecrls=yes in the config setup section
2474 of ipsec.conf. The dynamically fetched CRLs are stored under
2475 a unique file name containing the issuer's subjectKeyID
2476 in /etc/ipsec.d/crls.
2478 - Applied a one-line patch courtesy of Michael Richardson
2479 from the Openswan project which fixes the kernel-oops
2480 in KLIPS when an snmp daemon is running on the same box.
2486 - Eliminated null length CRL distribution point strings.
2488 - Fixed a trust path evaluation bug introduced with 2.4.3
2494 - Improved the joint OCSP / CRL revocation policy.
2495 OCSP responses have precedence over CRL entries.
2497 - Introduced support of CRLv2 reason codes.
2499 - Fixed a bug with key-pad equipped readers which caused
2500 pluto to prompt for the pin via the console when the first
2501 occasion to enter the pin via the key-pad was missed.
2503 - When pluto is built with LDAP_V3 enabled, the library
2504 liblber required by newer versions of openldap is now
2511 - Added the _updown_espmark template which requires all
2512 incoming ESP traffic to be marked with a default mark
2515 - Introduced the pkcs11keepstate parameter in the config setup
2516 section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11
2517 session and login states are kept as long as possible during
2518 the lifetime of pluto. This means that a PIN entry via a key
2519 pad has to be done only once.
2521 - Introduced the pkcs11module parameter in the config setup
2522 section of ipsec.conf which specifies the PKCS#11 module
2523 to be used with smart cards. Example:
2525 pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo
2527 - Added support of smartcard readers equipped with a PIN pad.
2529 - Added patch by Jay Pfeifer which detects when netkey
2530 modules have been statically built into the Linux 2.6 kernel.
2532 - Added two patches by Herbert Xu. The first uses ip xfrm
2533 instead of setkey to flush the IPsec policy database. The
2534 second sets the optional flag in inbound IPComp SAs only.
2536 - Applied Ulrich Weber's patch which fixes an interoperability
2537 problem between native IPsec and KLIPS systems caused by
2538 setting the replay window to 32 instead of 0 for ipcomp.
2544 - Fixed a bug which caused an unwanted Mode Config request
2545 to be initiated in the case where "right" was used to denote
2546 the local side in ipsec.conf and "left" the remote side,
2547 contrary to the recommendation that "right" be remote and
2554 - updated Vendor ID to strongSwan-2.4.0
2556 - updated copyright statement to include David Buechi and
2563 - strongSwan now communicates with attached smartcards and
2564 USB crypto tokens via the standardized PKCS #11 interface.
2565 By default the OpenSC library from www.opensc.org is used
2566 but any other PKCS#11 library could be dynamically linked.
2567 strongSwan's PKCS#11 API was implemented by David Buechi
2568 and Michael Meier, both graduates of the Zurich University
2569 of Applied Sciences in Winterthur, Switzerland.
2571 - When a %trap eroute is triggered by an outgoing IP packet
2572 then the native IPsec stack of the Linux 2.6 kernel [often/
2573 always?] returns an XFRM_ACQUIRE message with an undefined
2574 protocol family field and the connection setup fails.
2575 As a workaround IPv4 (AF_INET) is now assumed.
2577 - the results of the UML test scenarios are now enhanced
2578 with block diagrams of the virtual network topology used
2579 in a particular test.
2585 - fixed IV used to decrypt informational messages.
2586 This bug was introduced with Mode Config functionality.
2588 - fixed NCP Vendor ID.
2590 - undid one of Ulrich Weber's maximum udp size patches
2591 because it caused a segmentation fault with NAT-ed
2594 - added UML scenarios wildcards and attr-cert which
2595 demonstrate the implementation of IPsec policies based
2596 on wildcard parameters contained in Distinguished Names and
2597 on X.509 attribute certificates, respectively.
2603 - Added basic Mode Config functionality
2605 - Added Mathieu Lafon's patch which upgrades the status of
2606 the NAT-Traversal implementation to RFC 3947.
2608 - The _startklips script now also loads the xfrm4_tunnel
2611 - Added Ulrich Weber's netlink replay window size and
2612 maximum udp size patches.
2614 - UML testing now uses the Linux 2.6.10 UML kernel by default.
2620 - Eric Marchionni and Patrik Rayo, both recent graduates from
2621 the Zuercher Hochschule Winterthur in Switzerland, created a
2622 User-Mode-Linux test setup for strongSwan. For more details
2623 please read the INSTALL and README documents in the testing
2626 - Full support of group attributes based on X.509 attribute
2627 certificates. Attribute certificates can be generated
2628 using the openac facility. For more details see
2632 The group attributes can be used in connection definitions
2633 in order to give IPsec access to specific user groups.
2634 This is done with the new parameter left|rightgroups as in
2636 rightgroups="Research, Sales"
2638 giving access to users possessing the group attributes
2639 Research or Sales, only.
2641 - In Quick Mode clients with subnet mask /32 are now
2642 coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should
2643 fix rekeying problems with the SafeNet/SoftRemote and NCP
2644 Secure Entry Clients.
2646 - Changed the defaults of the ikelifetime and keylife parameters
2647 to 3h and 1h, respectively. The maximum allowable values are
2648 now both set to 24 h.
2650 - Suppressed notification wars between two IPsec peers that
2651 could e.g. be triggered by incorrect ISAKMP encryption.
2653 - Public RSA keys can now have identical IDs if either the
2654 issuing CA or the serial number is different. The serial
2655 number of a certificate is now shown by the command
2657 ipsec auto --listpubkeys
2663 - Added Tuomo Soini's sourceip feature which allows a strongSwan
2664 roadwarrior to use a fixed Virtual IP (see README section 2.6)
2665 and reduces the well-known four tunnel case on VPN gateways to
2666 a single tunnel definition (see README section 2.4).
2668 - Fixed a bug occurring with NAT-Traversal enabled when the responder
2669 suddenly turns initiator and the initiator cannot find a matching
2670 connection because of the floated IKE port 4500.
2672 - Removed misleading ipsec verify command from barf.
2674 - Running under the native IP stack, ipsec --version now shows
2675 the Linux kernel version (courtesy to the Openswan project).
2681 - Introduced the ipsec auto --listalgs monitoring command which lists
2682 all currently registered IKE and ESP algorithms.
2684 - Fixed a bug in the ESP algorithm selection occurring when the strict flag
2685 is set and the first proposed transform does not match.
2687 - Fixed another deadlock in the use of the lock_certs_and_keys() mutex,
2688 occurring when a smartcard is present.
2690 - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event.
2692 - Fixed the printing of the notification names (null)
2694 - Applied another of Herbert Xu's Netlink patches.
2700 - Support of Dead Peer Detection. The connection parameter
2702 dpdaction=clear|hold
2704 activates DPD for the given connection.
2706 - The default Opportunistic Encryption (OE) policy groups are not
2707 automatically included anymore. Those wishing to activate OE can include
2708 the policy group with the following statement in ipsec.conf:
2710 include /etc/ipsec.d/examples/oe.conf
2712 The default for [right|left]rsasigkey is now set to %cert.
2714 - strongSwan now has a Vendor ID of its own which can be activated
2715 using the compile option VENDORID
2717 - Applied Herbert Xu's patch which sets the compression algorithm correctly.
2719 - Applied Herbert Xu's patch fixing an ESPINUDP problem
2721 - Applied Herbert Xu's patch setting source/destination port numbers.
2723 - Reapplied one of Herbert Xu's NAT-Traversal patches which got
2724 lost during the migration from SuperFreeS/WAN.
2726 - Fixed a deadlock in the use of the lock_certs_and_keys() mutex.
2728 - Fixed the unsharing of alg parameters when instantiating group
2735 - Thomas Walpuski made me aware of a potential DoS attack via
2736 a PKCS#7-wrapped certificate bundle which could overwrite valid CA
2737 certificates in Pluto's authority certificate store. This vulnerability
2738 was fixed by establishing trust in CA candidate certificates up to a
2739 trusted root CA prior to insertion into Pluto's chained list.
2741 - replaced the --assign option by the -v option in the auto awk script
2742 in order to make it run with mawk under debian/woody.
2748 - Split of the status information between ipsec auto --status (concise)
2749 and ipsec auto --statusall (verbose). Both commands can be used with
2750 an optional connection selector:
2752 ipsec auto --status[all] <connection_name>
2754 - Added the description of X.509 related features to the ipsec_auto(8)
2757 - Hardened the ASN.1 parser in debug mode, especially the printing
2758 of malformed distinguished names.
2760 - The size of an RSA public key received in a certificate is now restricted to
2762 512 bits <= modulus length <= 8192 bits.
2764 - Fixed the debug mode enumeration.
2770 - Fixed another PKCS#7 vulnerability which could lead to an
2771 endless loop while following the X.509 trust chain.
2777 - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski
2778 that accepted end certificates having identical issuer and subject
2779 distinguished names in a multi-tier X.509 trust chain.
2785 - Removed all remaining references to ipsec_netlink.h in KLIPS.
2791 - The new "ca" section allows to define the following parameters:
2794 cacert=koolCA.pem # cacert of kool CA
2795 ocspuri=http://ocsp.kool.net:8001 # ocsp server
2796 ldapserver=ldap.kool.net # default ldap server
2797 crluri=http://www.kool.net/kool.crl # crl distribution point
2798 crluri2="ldap:///O=Kool, C= .." # crl distribution point #2
2799 auto=add # add, ignore
2801 The ca definitions can be monitored via the command
2803 ipsec auto --listcainfos
2805 - Fixed cosmetic corruption of /proc filesystem by integrating
2806 D. Hugh Redelmeier's freeswan-2.06 kernel fixes.
2812 - Added support for the 818043 NAT-Traversal update of Microsoft's
2813 Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode.
2815 - A symbolic link to libcrypto is now added in the kernel sources
2816 during kernel compilation
2818 - Fixed a couple of 64 bit issues (mostly casts to int).
2819 Thanks to Ken Bantoft who checked my sources on a 64 bit platform.
2821 - Replaced s[n]printf() statements in the kernel by ipsec_snprintf().
2822 Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro
2823 of the FreeS/WAN team who solved this problem with the 2.4.25 kernel.
2829 - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName
2830 certificate extension which contains no generalName item) can cause
2831 a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has
2832 been hardened to make it more robust against malformed ASN.1 objects.
2834 - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native
2835 Linux 2.6 IPsec stack.
2841 - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12