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