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