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