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