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