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