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