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