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