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