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