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