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