]> git.ipfire.org Git - thirdparty/strongswan.git/blob - NEWS
changes in 4.2.12
[thirdparty/strongswan.git] / NEWS
1 strongswan-4.2.12
2 '----------------
3
4 - Support of the EAP-MSCHAPv2 protocol enabled by the option
5 --enable-eap-mschapv2. Requires the MD4 hash algorithm enabled
6 either by --enable-md4 or --enable-openssl.
7
8 - Assignment of up to two DNS and up to two WINS servers to peers via
9 the IKEv2 Configuration Payload (CP). The IPv4 or IPv6 nameserver
10 addresses are defined in strongswan.conf.
11
12 - The strongSwan applet for the Gnome NetworkManager is now built and
13 distributed as a separate tarball under the name NetworkManager-strongswan.
14
15
16 strongswan-4.2.11
17 -----------------
18
19 - Fixed ESP NULL encryption broken by the refactoring of keymat.c.
20 Also introduced proper initialization and disposal of keying material.
21
22 - Fixed the missing listing of connection definitions in ipsec statusall
23 broken by an unfortunate local variable overload.
24
25
26 strongswan-4.2.10
27 -----------------
28
29 - Several performance improvements to handle thousands of tunnels with almost
30 linear upscaling. All relevant data structures have been replaced by faster
31 counterparts with better lookup times.
32
33 - Better parallelization to run charon on multiple cores. Due to improved
34 ressource locking and other optimizations the daemon can take full
35 advantage of 16 or even more cores.
36
37 - The load-tester plugin can use a NULL Diffie-Hellman group and simulate
38 unique identities and certificates by signing peer certificates using a CA
39 on the fly.
40
41 - The redesigned stroke in-memory IP pool handles leases. The "ipsec leases"
42 command queries assigned leases.
43
44 - Added support for smartcards in charon by using the ENGINE API provided by
45 OpenSSL, based on patches by Michael Roßberg.
46
47 - The Padlock plugin supports the hardware RNG found on VIA CPUs to provide a
48 reliable source of randomness.
49
50 strongswan-4.2.9
51 ----------------
52
53 - Flexible configuration of logging subsystem allowing to log to multiple
54 syslog facilities or to files using fine-grained log levels for each target.
55
56 - Load testing plugin to do stress testing of the IKEv2 daemon against self
57 or another host. Found and fixed issues during tests in the multi-threaded
58 use of the OpenSSL plugin.
59
60 - Added profiling code to synchronization primitives to find bottlenecks if
61 running on multiple cores. Found and fixed an issue where parts of the
62 Diffie-Hellman calculation acquired an exclusive lock. This greatly improves
63 parallelization to multiple cores.
64
65 - updown script invocation has been separated into a plugin of its own to
66 further slim down the daemon core.
67
68 - Separated IKE_SA/CHILD_SA key derivation process into a closed system,
69 allowing future implementations to use a secured environment in e.g. kernel
70 memory or hardware.
71
72 - The kernel interface of charon has been modularized. XFRM NETLINK (default)
73 and PFKEY (--enable-kernel-pfkey) interface plugins for the native IPsec
74 stack of the Linux 2.6 kernel as well as a PFKEY interface for the KLIPS
75 IPsec stack (--enable-kernel-klips) are provided.
76
77 - Basic Mobile IPv6 support has been introduced, securing Binding Update
78 messages as well as tunneled traffic between Mobile Node and Home Agent.
79 The installpolicy=no option allows peaceful cooperation with a dominant
80 mip6d daemon and the new type=transport_proxy implements the special MIPv6
81 IPsec transport proxy mode where the IKEv2 daemon uses the Care-of-Address
82 but the IPsec SA is set up for the Home Adress.
83
84 - Implemented migration of Mobile IPv6 connections using the KMADDRESS
85 field contained in XFRM_MSG_MIGRATE messages sent by the mip6d daemon
86 via the Linux 2.6.28 (or appropriately patched) kernel.
87
88
89 strongswan-4.2.8
90 ----------------
91
92 - IKEv2 charon daemon supports authentication based on raw public keys
93 stored in the SQL database backend. The ipsec listpubkeys command
94 lists the available raw public keys via the stroke interface.
95
96 - Several MOBIKE improvements: Detect changes in NAT mappings in DPD exchanges,
97 handle events if kernel detects NAT mapping changes in UDP-encapsulated
98 ESP packets (requires kernel patch), reuse old addesses in MOBIKE updates as
99 long as possible and other fixes.
100
101 - Fixed a bug in addr_in_subnet() which caused insertion of wrong source
102 routes for destination subnets having netwmasks not being a multiple of 8 bits.
103 Thanks go to Wolfgang Steudel, TU Ilmenau for reporting this bug.
104
105
106 strongswan-4.2.7
107 ----------------
108
109 - Fixed a Denial-of-Service vulnerability where an IKE_SA_INIT message with
110 a KE payload containing zeroes only can cause a crash of the IKEv2 charon
111 daemon due to a NULL pointer returned by the mpz_export() function of the
112 GNU Multiprecision Library (GMP). Thanks go to Mu Dynamics Research Labs
113 for making us aware of this problem.
114
115 - The new agent plugin provides a private key implementation on top of an
116 ssh-agent.
117
118 - The NetworkManager plugin has been extended to support certificate client
119 authentication using RSA keys loaded from a file or using ssh-agent.
120
121 - Daemon capability dropping has been ported to libcap and must be enabled
122 explicitly --with-capabilities=libcap. Future version will support the
123 newer libcap2 library.
124
125 - ipsec listalgs lists the IKEv2 cryptografic algorithms registered with the
126 charon keying daemon.
127
128
129 strongswan-4.2.6
130 ----------------
131
132 - A NetworkManager plugin allows GUI-based configuration of road-warrior
133 clients in a simple way. It features X509 based gateway authentication
134 and EAP client authentication, tunnel setup/teardown and storing passwords
135 in the Gnome Keyring.
136
137 - A new EAP-GTC plugin implements draft-sheffer-ikev2-gtc-00.txt and allows
138 username/password authentication against any PAM service on the gateway.
139 The new EAP method interacts nicely with the NetworkManager plugin and allows
140 client authentication against e.g. LDAP.
141
142 - Improved support for the EAP-Identity method. The new ipsec.conf eap_identity
143 parameter defines an additional identity to pass to the server in EAP
144 authentication.
145
146 - The "ipsec statusall" command now lists CA restrictions, EAP
147 authentication types and EAP identities.
148
149 - Fixed two multithreading deadlocks occurring when starting up
150 several hundred tunnels concurrently.
151
152 - Fixed the --enable-integrity-test configure option which
153 computes a SHA-1 checksum over the libstrongswan library.
154
155
156 strongswan-4.2.5
157 ----------------
158
159 - Consistent logging of IKE and CHILD SAs at the audit (AUD) level.
160
161 - Improved the performance of the SQL-based virtual IP address pool
162 by introducing an additional addresses table. The leases table
163 storing only history information has become optional and can be
164 disabled by setting charon.plugins.sql.lease_history = no in
165 strongswan.conf.
166
167 - The XFRM_STATE_AF_UNSPEC flag added to xfrm.h allows IPv4-over-IPv6
168 and IPv6-over-IPv4 tunnels with the 2.6.26 and later Linux kernels.
169
170 - management of different virtual IP pools for different
171 network interfaces have become possible.
172
173 - fixed a bug which prevented the assignment of more than 256
174 virtual IP addresses from a pool managed by an sql database.
175
176 - fixed a bug which did not delete own IPCOMP SAs in the kernel.
177
178
179 strongswan-4.2.4
180 ----------------
181
182 - Added statistics functions to ipsec pool --status and ipsec pool --leases
183 and input validation checks to various ipsec pool commands.
184
185 - ipsec statusall now lists all loaded charon plugins and displays
186 the negotiated IKEv2 cipher suite proposals.
187
188 - The openssl plugin supports the elliptic curve Diffie-Hellman groups
189 19, 20, 21, 25, and 26.
190
191 - The openssl plugin supports ECDSA authentication using elliptic curve
192 X.509 certificates.
193
194 - Fixed a bug in stroke which caused multiple charon threads to close
195 the file descriptors during packet transfers over the stroke socket.
196
197 - ESP sequence numbers are now migrated in IPsec SA updates handled by
198 MOBIKE. Works only with Linux kernels >= 2.6.17.
199
200
201 strongswan-4.2.3
202 ----------------
203
204 - Fixed the strongswan.conf path configuration problem that occurred when
205 --sysconfig was not set explicitly in ./configure.
206
207 - Fixed a number of minor bugs that where discovered during the 4th
208 IKEv2 interoperability workshop in San Antonio, TX.
209
210
211 strongswan-4.2.2
212 ----------------
213
214 - Plugins for libstrongswan and charon can optionally be loaded according
215 to a configuration in strongswan.conf. Most components provide a
216 "load = " option followed by a space separated list of plugins to load.
217 This allows e.g. the fallback from a hardware crypto accelerator to
218 to software-based crypto plugins.
219
220 - Charons SQL plugin has been extended by a virtual IP address pool.
221 Configurations with a rightsourceip=%poolname setting query a SQLite or
222 MySQL database for leases. The "ipsec pool" command helps in administrating
223 the pool database. See ipsec pool --help for the available options
224
225 - The Authenticated Encryption Algorithms AES-CCM-8/12/16 and AES-GCM-8/12/16
226 for ESP are now supported starting with the Linux 2.6.25 kernel. The
227 syntax is e.g. esp=aes128ccm12 or esp=aes256gcm16.
228
229
230 strongswan-4.2.1
231 ----------------
232
233 - Support for "Hash and URL" encoded certificate payloads has been implemented
234 in the IKEv2 daemon charon. Using the "certuribase" option of a CA section
235 allows to assign a base URL to all certificates issued by the specified CA.
236 The final URL is then built by concatenating that base and the hex encoded
237 SHA1 hash of the DER encoded certificate. Note that this feature is disabled
238 by default and must be enabled using the option "charon.hash_and_url".
239
240 - The IKEv2 daemon charon now supports the "uniqueids" option to close multiple
241 IKE_SAs with the same peer. The option value "keep" prefers existing
242 connection setups over new ones, where the value "replace" replaces existing
243 connections.
244
245 - The crypto factory in libstrongswan additionaly supports random number
246 generators, plugins may provide other sources of randomness. The default
247 plugin reads raw random data from /dev/(u)random.
248
249 - Extended the credential framework by a caching option to allow plugins
250 persistent caching of fetched credentials. The "cachecrl" option has been
251 re-implemented.
252
253 - The new trustchain verification introduced in 4.2.0 has been parallelized.
254 Threads fetching CRL or OCSP information no longer block other threads.
255
256 - A new IKEv2 configuration attribute framework has been introduced allowing
257 plugins to provide virtual IP addresses, and in the future, other
258 configuration attribute services (e.g. DNS/WINS servers).
259
260 - The stroke plugin has been extended to provide virtual IP addresses from
261 a pool defined in ipsec.conf. The "rightsourceip" parameter now accepts
262 address pools in CIDR notation (e.g. 10.1.1.0/24). The parameter also accepts
263 the value "%poolname", where "poolname" identifies a pool provided by a
264 separate plugin.
265
266 - Fixed compilation on uClibc and a couple of other minor bugs.
267
268 - Set DPD defaults in ipsec starter to dpd_delay=30s and dpd_timeout=150s.
269
270 - The IKEv1 pluto daemon now supports the ESP encryption algorithm CAMELLIA
271 with key lengths of 128, 192, and 256 bits, as well as the authentication
272 algorithm AES_XCBC_MAC. Configuration example: esp=camellia192-aesxcbc.
273
274
275 strongswan-4.2.0
276 ----------------
277
278 - libstrongswan has been modularized to attach crypto algorithms,
279 credential implementations (keys, certificates) and fetchers dynamically
280 through plugins. Existing code has been ported to plugins:
281 - RSA/Diffie-Hellman implementation using the GNU Multi Precision library
282 - X509 certificate system supporting CRLs, OCSP and attribute certificates
283 - Multiple plugins providing crypto algorithms in software
284 - CURL and OpenLDAP fetcher
285
286 - libstrongswan gained a relational database API which uses pluggable database
287 providers. Plugins for MySQL and SQLite are available.
288
289 - The IKEv2 keying daemon charon is more extensible. Generic plugins may provide
290 connection configuration, credentials and EAP methods or control the daemon.
291 Existing code has been ported to plugins:
292 - EAP-AKA, EAP-SIM, EAP-MD5 and EAP-Identity
293 - stroke configuration, credential and control (compatible to pluto)
294 - XML bases management protocol to control and query the daemon
295 The following new plugins are available:
296 - An experimental SQL configuration, credential and logging plugin on
297 top of either MySQL or SQLite
298 - A unit testing plugin to run tests at daemon startup
299
300 - The authentication and credential framework in charon has been heavily
301 refactored to support modular credential providers, proper
302 CERTREQ/CERT payload exchanges and extensible authorization rules.
303
304 - The framework of strongSwan Manager has envolved to the web application
305 framework libfast (FastCGI Application Server w/ Templates) and is usable
306 by other applications.
307
308
309 strongswan-4.1.11
310 -----------------
311
312 - IKE rekeying in NAT situations did not inherit the NAT conditions
313 to the rekeyed IKE_SA so that the UDP encapsulation was lost with
314 the next CHILD_SA rekeying.
315
316 - Wrong type definition of the next_payload variable in id_payload.c
317 caused an INVALID_SYNTAX error on PowerPC platforms.
318
319 - Implemented IKEv2 EAP-SIM server and client test modules that use
320 triplets stored in a file. For details on the configuration see
321 the scenario 'ikev2/rw-eap-sim-rsa'.
322
323
324 strongswan-4.1.10
325 -----------------
326
327 - Fixed error in the ordering of the certinfo_t records in the ocsp cache that
328 caused multiple entries of the same serial number to be created.
329
330 - Implementation of a simple EAP-MD5 module which provides CHAP
331 authentication. This may be interesting in conjunction with certificate
332 based server authentication, as weak passwords can't be brute forced
333 (in contradiction to traditional IKEv2 PSK).
334
335 - A complete software based implementation of EAP-AKA, using algorithms
336 specified in 3GPP2 (S.S0055). This implementation does not use an USIM,
337 but reads the secrets from ipsec.secrets. Make sure to read eap_aka.h
338 before using it.
339
340 - Support for vendor specific EAP methods using Expanded EAP types. The
341 interface to EAP modules has been slightly changed, so make sure to
342 check the changes if you're already rolling your own modules.
343
344
345 strongswan-4.1.9
346 ----------------
347
348 - The default _updown script now dynamically inserts and removes ip6tables
349 firewall rules if leftfirewall=yes is set in IPv6 connections. New IPv6
350 net-net and roadwarrior (PSK/RSA) scenarios for both IKEv1 and IKEV2 were
351 added.
352
353 - Implemented RFC4478 repeated authentication to force EAP/Virtual-IP clients
354 to reestablish an IKE_SA within a given timeframe.
355
356 - strongSwan Manager supports configuration listing, initiation and termination
357 of IKE and CHILD_SAs.
358
359 - Fixes and improvements to multithreading code.
360
361 - IKEv2 plugins have been renamed to libcharon-* to avoid naming conflicts.
362 Make sure to remove the old plugins in $libexecdir/ipsec, otherwise they get
363 loaded twice.
364
365
366 strongswan-4.1.8
367 ----------------
368
369 - Removed recursive pthread mutexes since uClibc doesn't support them.
370
371
372 strongswan-4.1.7
373 ----------------
374
375 - In NAT traversal situations and multiple queued Quick Modes,
376 those pending connections inserted by auto=start after the
377 port floating from 500 to 4500 were erronously deleted.
378
379 - Added a "forceencaps" connection parameter to enforce UDP encapsulation
380 to surmount restrictive firewalls. NAT detection payloads are faked to
381 simulate a NAT situation and trick the other peer into NAT mode (IKEv2 only).
382
383 - Preview of strongSwan Manager, a web based configuration and monitoring
384 application. It uses a new XML control interface to query the IKEv2 daemon
385 (see http://trac.strongswan.org/wiki/Manager).
386
387 - Experimental SQLite configuration backend which will provide the configuration
388 interface for strongSwan Manager in future releases.
389
390 - Further improvements to MOBIKE support.
391
392
393 strongswan-4.1.6
394 ----------------
395
396 - Since some third party IKEv2 implementations run into
397 problems with strongSwan announcing MOBIKE capability per
398 default, MOBIKE can be disabled on a per-connection-basis
399 using the mobike=no option. Whereas mobike=no disables the
400 sending of the MOBIKE_SUPPORTED notification and the floating
401 to UDP port 4500 with the IKE_AUTH request even if no NAT
402 situation has been detected, strongSwan will still support
403 MOBIKE acting as a responder.
404
405 - the default ipsec routing table plus its corresponding priority
406 used for inserting source routes has been changed from 100 to 220.
407 It can be configured using the --with-ipsec-routing-table and
408 --with-ipsec-routing-table-prio options.
409
410 - the --enable-integrity-test configure option tests the
411 integrity of the libstrongswan crypto code during the charon
412 startup.
413
414 - the --disable-xauth-vid configure option disables the sending
415 of the XAUTH vendor ID. This can be used as a workaround when
416 interoperating with some Windows VPN clients that get into
417 trouble upon reception of an XAUTH VID without eXtended
418 AUTHentication having been configured.
419
420 - ipsec stroke now supports the rereadsecrets, rereadaacerts,
421 rereadacerts, and listacerts options.
422
423
424 strongswan-4.1.5
425 ----------------
426
427 - If a DNS lookup failure occurs when resolving right=%<FQDN>
428 or right=<FQDN> combined with rightallowany=yes then the
429 connection is not updated by ipsec starter thus preventing
430 the disruption of an active IPsec connection. Only if the DNS
431 lookup successfully returns with a changed IP address the
432 corresponding connection definition is updated.
433
434 - Routes installed by the keying daemons are now in a separate
435 routing table with the ID 100 to avoid conflicts with the main
436 table. Route lookup for IKEv2 traffic is done in userspace to ignore
437 routes installed for IPsec, as IKE traffic shouldn't get encapsulated.
438
439
440 strongswan-4.1.4
441 ----------------
442
443 - The pluto IKEv1 daemon now exhibits the same behaviour as its
444 IKEv2 companion charon by inserting an explicit route via the
445 _updown script only if a sourceip exists. This is admissible
446 since routing through the IPsec tunnel is handled automatically
447 by NETKEY's IPsec policies. As a consequence the left|rightnexthop
448 parameter is not required any more.
449
450 - The new IKEv1 parameter right|leftallowany parameters helps to handle
451 the case where both peers possess dynamic IP addresses that are
452 usually resolved using DynDNS or a similar service. The configuration
453
454 right=peer.foo.bar
455 rightallowany=yes
456
457 can be used by the initiator to start up a connection to a peer
458 by resolving peer.foo.bar into the currently allocated IP address.
459 Thanks to the rightallowany flag the connection behaves later on
460 as
461
462 right=%any
463
464 so that the peer can rekey the connection as an initiator when his
465 IP address changes. An alternative notation is
466
467 right=%peer.foo.bar
468
469 which will implicitly set rightallowany=yes.
470
471 - ipsec starter now fails more gracefully in the presence of parsing
472 errors. Flawed ca and conn section are discarded and pluto is started
473 if non-fatal errors only were encountered. If right=%peer.foo.bar
474 cannot be resolved by DNS then right=%any will be used so that passive
475 connections as a responder are still possible.
476
477 - The new pkcs11initargs parameter that can be placed in the
478 setup config section of /etc/ipsec.conf allows the definition
479 of an argument string that is used with the PKCS#11 C_Initialize()
480 function. This non-standard feature is required by the NSS softoken
481 library. This patch was contributed by Robert Varga.
482
483 - Fixed a bug in ipsec starter introduced by strongswan-2.8.5
484 which caused a segmentation fault in the presence of unknown
485 or misspelt keywords in ipsec.conf. This bug fix was contributed
486 by Robert Varga.
487
488 - Partial support for MOBIKE in IKEv2. The initiator acts on interface/
489 address configuration changes and updates IKE and IPsec SAs dynamically.
490
491
492 strongswan-4.1.3
493 ----------------
494
495 - IKEv2 peer configuration selection now can be based on a given
496 certification authority using the rightca= statement.
497
498 - IKEv2 authentication based on RSA signatures now can handle multiple
499 certificates issued for a given peer ID. This allows a smooth transition
500 in the case of a peer certificate renewal.
501
502 - IKEv2: Support for requesting a specific virtual IP using leftsourceip on the
503 client and returning requested virtual IPs using rightsourceip=%config
504 on the server. If the server does not support configuration payloads, the
505 client enforces its leftsourceip parameter.
506
507 - The ./configure options --with-uid/--with-gid allow pluto and charon
508 to drop their privileges to a minimum and change to an other UID/GID. This
509 improves the systems security, as a possible intruder may only get the
510 CAP_NET_ADMIN capability.
511
512 - Further modularization of charon: Pluggable control interface and
513 configuration backend modules provide extensibility. The control interface
514 for stroke is included, and further interfaces using DBUS (NetworkManager)
515 or XML are on the way. A backend for storing configurations in the daemon
516 is provided and more advanced backends (using e.g. a database) are trivial
517 to implement.
518
519 - Fixed a compilation failure in libfreeswan occuring with Linux kernel
520 headers > 2.6.17.
521
522
523 strongswan-4.1.2
524 ----------------
525
526 - Support for an additional Diffie-Hellman exchange when creating/rekeying
527 a CHILD_SA in IKEv2 (PFS). PFS is enabled when the proposal contains a
528 DH group (e.g. "esp=aes128-sha1-modp1536"). Further, DH group negotiation
529 is implemented properly for rekeying.
530
531 - Support for the AES-XCBC-96 MAC algorithm for IPsec SAs when using IKEv2
532 (requires linux >= 2.6.20). It is enabled using e.g. "esp=aes256-aesxcbc".
533
534 - Working IPv4-in-IPv6 and IPv6-in-IPv4 tunnels for linux >= 2.6.21.
535
536 - Added support for EAP modules which do not establish an MSK.
537
538 - Removed the dependencies from the /usr/include/linux/ headers by
539 including xfrm.h, ipsec.h, and pfkeyv2.h in the distribution.
540
541 - crlNumber is now listed by ipsec listcrls
542
543 - The xauth_modules.verify_secret() function now passes the
544 connection name.
545
546
547 strongswan-4.1.1
548 ----------------
549
550 - Server side cookie support. If to may IKE_SAs are in CONNECTING state,
551 cookies are enabled and protect against DoS attacks with faked source
552 addresses. Number of IKE_SAs in CONNECTING state is also limited per
553 peer address to avoid resource exhaustion. IKE_SA_INIT messages are
554 compared to properly detect retransmissions and incoming retransmits are
555 detected even if the IKE_SA is blocked (e.g. doing OCSP fetches).
556
557 - The IKEv2 daemon charon now supports dynamic http- and ldap-based CRL
558 fetching enabled by crlcheckinterval > 0 and caching fetched CRLs
559 enabled by cachecrls=yes.
560
561 - Added the configuration options --enable-nat-transport which enables
562 the potentially insecure NAT traversal for IPsec transport mode and
563 --disable-vendor-id which disables the sending of the strongSwan
564 vendor ID.
565
566 - Fixed a long-standing bug in the pluto IKEv1 daemon which caused
567 a segmentation fault if a malformed payload was detected in the
568 IKE MR2 message and pluto tried to send an encrypted notification
569 message.
570
571 - Added the NATT_IETF_02_N Vendor ID in order to support IKEv1 connections
572 with Windows 2003 Server which uses a wrong VID hash.
573
574
575 strongswan-4.1.0
576 ----------------
577
578 - Support of SHA2_384 hash function for protecting IKEv1
579 negotiations and support of SHA2 signatures in X.509 certificates.
580
581 - Fixed a serious bug in the computation of the SHA2-512 HMAC
582 function. Introduced automatic self-test of all IKEv1 hash
583 and hmac functions during pluto startup. Failure of a self-test
584 currently issues a warning only but does not exit pluto [yet].
585
586 - Support for SHA2-256/384/512 PRF and HMAC functions in IKEv2.
587
588 - Full support of CA information sections. ipsec listcainfos
589 now shows all collected crlDistributionPoints and OCSP
590 accessLocations.
591
592 - Support of the Online Certificate Status Protocol (OCSP) for IKEv2.
593 This feature requires the HTTP fetching capabilities of the libcurl
594 library which must be enabled by setting the --enable-http configure
595 option.
596
597 - Refactored core of the IKEv2 message processing code, allowing better
598 code reuse and separation.
599
600 - Virtual IP support in IKEv2 using INTERNAL_IP4/6_ADDRESS configuration
601 payload. Additionally, the INTERNAL_IP4/6_DNS attribute is interpreted
602 by the requestor and installed in a resolv.conf file.
603
604 - The IKEv2 daemon charon installs a route for each IPsec policy to use
605 the correct source address even if an application does not explicitly
606 specify it.
607
608 - Integrated the EAP framework into charon which loads pluggable EAP library
609 modules. The ipsec.conf parameter authby=eap initiates EAP authentication
610 on the client side, while the "eap" parameter on the server side defines
611 the EAP method to use for client authentication.
612 A generic client side EAP-Identity module and an EAP-SIM authentication
613 module using a third party card reader implementation are included.
614
615 - Added client side support for cookies.
616
617 - Integrated the fixes done at the IKEv2 interoperability bakeoff, including
618 strict payload order, correct INVALID_KE_PAYLOAD rejection and other minor
619 fixes to enhance interoperability with other implementations.
620
621
622 strongswan-4.0.7
623 ----------------
624
625 - strongSwan now interoperates with the NCP Secure Entry Client,
626 the Shrew Soft VPN Client, and the Cisco VPN client, doing both
627 XAUTH and Mode Config.
628
629 - UNITY attributes are now recognized and UNITY_BANNER is set
630 to a default string.
631
632
633 strongswan-4.0.6
634 ----------------
635
636 - IKEv1: Support for extended authentication (XAUTH) in combination
637 with ISAKMP Main Mode RSA or PSK authentication. Both client and
638 server side were implemented. Handling of user credentials can
639 be done by a run-time loadable XAUTH module. By default user
640 credentials are stored in ipsec.secrets.
641
642 - IKEv2: Support for reauthentication when rekeying
643
644 - IKEv2: Support for transport mode
645
646 - fixed a lot of bugs related to byte order
647
648 - various other bugfixes
649
650
651 strongswan-4.0.5
652 ----------------
653
654 - IKEv1: Implementation of ModeConfig push mode via the new connection
655 keyword modeconfig=push allows interoperability with Cisco VPN gateways.
656
657 - IKEv1: The command ipsec statusall now shows "DPD active" for all
658 ISAKMP SAs that are under active Dead Peer Detection control.
659
660 - IKEv2: Charon's logging and debugging framework has been completely rewritten.
661 Instead of logger, special printf() functions are used to directly
662 print objects like hosts (%H) identifications (%D), certificates (%Q),
663 etc. The number of debugging levels have been reduced to:
664
665 0 (audit), 1 (control), 2 (controlmore), 3 (raw), 4 (private)
666
667 The debugging levels can either be specified statically in ipsec.conf as
668
669 config setup
670 charondebug="lib 1, cfg 3, net 2"
671
672 or changed at runtime via stroke as
673
674 ipsec stroke loglevel cfg 2
675
676
677 strongswan-4.0.4
678 ----------------
679
680 - Implemented full support for IPv6-in-IPv6 tunnels.
681
682 - Added configuration options for dead peer detection in IKEv2. dpd_action
683 types "clear", "hold" and "restart" are supported. The dpd_timeout
684 value is not used, as the normal retransmission policy applies to
685 detect dead peers. The dpd_delay parameter enables sending of empty
686 informational message to detect dead peers in case of inactivity.
687
688 - Added support for preshared keys in IKEv2. PSK keys configured in
689 ipsec.secrets are loaded. The authby parameter specifies the authentication
690 method to authentificate ourself, the other peer may use PSK or RSA.
691
692 - Changed retransmission policy to respect the keyingtries parameter.
693
694 - Added private key decryption. PEM keys encrypted with AES-128/192/256
695 or 3DES are supported.
696
697 - Implemented DES/3DES algorithms in libstrongswan. 3DES can be used to
698 encrypt IKE traffic.
699
700 - Implemented SHA-256/384/512 in libstrongswan, allows usage of certificates
701 signed with such a hash algorithm.
702
703 - Added initial support for updown scripts. The actions up-host/client and
704 down-host/client are executed. The leftfirewall=yes parameter
705 uses the default updown script to insert dynamic firewall rules, a custom
706 updown script may be specified with the leftupdown parameter.
707
708
709 strongswan-4.0.3
710 ----------------
711
712 - Added support for the auto=route ipsec.conf parameter and the
713 ipsec route/unroute commands for IKEv2. This allows to set up IKE_SAs and
714 CHILD_SAs dynamically on demand when traffic is detected by the
715 kernel.
716
717 - Added support for rekeying IKE_SAs in IKEv2 using the ikelifetime parameter.
718 As specified in IKEv2, no reauthentication is done (unlike in IKEv1), only
719 new keys are generated using perfect forward secrecy. An optional flag
720 which enforces reauthentication will be implemented later.
721
722 - "sha" and "sha1" are now treated as synonyms in the ike= and esp=
723 algorithm configuration statements.
724
725
726 strongswan-4.0.2
727 ----------------
728
729 - Full X.509 certificate trust chain verification has been implemented.
730 End entity certificates can be exchanged via CERT payloads. The current
731 default is leftsendcert=always, since CERTREQ payloads are not supported
732 yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls.
733
734 - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2
735 would offer more possibilities for traffic selection, but the Linux kernel
736 currently does not support it. That's why we stick with these simple
737 ipsec.conf rules for now.
738
739 - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no
740 IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear,
741 dpddelay=60s).
742
743 - Initial NAT traversal support in IKEv2. Charon includes NAT detection
744 notify payloads to detect NAT routers between the peers. It switches
745 to port 4500, uses UDP encapsulated ESP packets, handles peer address
746 changes gracefully and sends keep alive message periodically.
747
748 - Reimplemented IKE_SA state machine for charon, which allows simultaneous
749 rekeying, more shared code, cleaner design, proper retransmission
750 and a more extensible code base.
751
752 - The mixed PSK/RSA roadwarrior detection capability introduced by the
753 strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal
754 payloads by the responder right before any defined IKE Main Mode state had
755 been established. Although any form of bad proposal syntax was being correctly
756 detected by the payload parser, the subsequent error handler didn't check
757 the state pointer before logging current state information, causing an
758 immediate crash of the pluto keying daemon due to a NULL pointer.
759
760
761 strongswan-4.0.1
762 ----------------
763
764 - Added algorithm selection to charon: New default algorithms for
765 ike=aes128-sha-modp2048, as both daemons support it. The default
766 for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles
767 the ike/esp parameter the same way as pluto. As this syntax does
768 not allow specification of a pseudo random function, the same
769 algorithm as for integrity is used (currently sha/md5). Supported
770 algorithms for IKE:
771 Encryption: aes128, aes192, aes256
772 Integrity/PRF: md5, sha (using hmac)
773 DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192
774 and for ESP:
775 Encryption: aes128, aes192, aes256, 3des, blowfish128,
776 blowfish192, blowfish256
777 Integrity: md5, sha1
778 More IKE encryption algorithms will come after porting libcrypto into
779 libstrongswan.
780
781 - initial support for rekeying CHILD_SAs using IKEv2. Currently no
782 perfect forward secrecy is used. The rekeying parameters rekey,
783 rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported
784 when using IKEv2. WARNING: charon currently is unable to handle
785 simultaneous rekeying. To avoid such a situation, use a large
786 rekeyfuzz, or even better, set rekey=no on one peer.
787
788 - support for host2host, net2net, host2net (roadwarrior) tunnels
789 using predefined RSA certificates (see uml scenarios for
790 configuration examples).
791
792 - new build environment featuring autotools. Features such
793 as HTTP, LDAP and smartcard support may be enabled using
794 the ./configure script. Changing install directories
795 is possible, too. See ./configure --help for more details.
796
797 - better integration of charon with ipsec starter, which allows
798 (almost) transparent operation with both daemons. charon
799 handles ipsec commands up, down, status, statusall, listall,
800 listcerts and allows proper load, reload and delete of connections
801 via ipsec starter.
802
803
804 strongswan-4.0.0
805 ----------------
806
807 - initial support of the IKEv2 protocol. Connections in
808 ipsec.conf designated by keyexchange=ikev2 are negotiated
809 by the new IKEv2 charon keying daemon whereas those marked
810 by keyexchange=ikev1 or the default keyexchange=ike are
811 handled thy the IKEv1 pluto keying daemon. Currently only
812 a limited subset of functions are available with IKEv2
813 (Default AES encryption, authentication based on locally
814 imported X.509 certificates, unencrypted private RSA keys
815 in PKCS#1 file format, limited functionality of the ipsec
816 status command).
817
818
819 strongswan-2.7.0
820 ----------------
821
822 - the dynamic iptables rules from the _updown_x509 template
823 for KLIPS and the _updown_policy template for NETKEY have
824 been merged into the default _updown script. The existing
825 left|rightfirewall keyword causes the automatic insertion
826 and deletion of ACCEPT rules for tunneled traffic upon
827 the successful setup and teardown of an IPsec SA, respectively.
828 left|rightfirwall can be used with KLIPS under any Linux 2.4
829 kernel or with NETKEY under a Linux kernel version >= 2.6.16
830 in conjuction with iptables >= 1.3.5. For NETKEY under a Linux
831 kernel version < 2.6.16 which does not support IPsec policy
832 matching yet, please continue to use a copy of the _updown_espmark
833 template loaded via the left|rightupdown keyword.
834
835 - a new left|righthostaccess keyword has been introduced which
836 can be used in conjunction with left|rightfirewall and the
837 default _updown script. By default leftfirewall=yes inserts
838 a bi-directional iptables FORWARD rule for a local client network
839 with a netmask different from 255.255.255.255 (single host).
840 This does not allow to access the VPN gateway host via its
841 internal network interface which is part of the client subnet
842 because an iptables INPUT and OUTPUT rule would be required.
843 lefthostaccess=yes will cause this additional ACCEPT rules to
844 be inserted.
845
846 - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal
847 payload is preparsed in order to find out whether the roadwarrior
848 requests PSK or RSA so that a matching connection candidate can
849 be found.
850
851
852 strongswan-2.6.4
853 ----------------
854
855 - the new _updown_policy template allows ipsec policy based
856 iptables firewall rules. Required are iptables version
857 >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes
858 the _updown_espmark template, so that no INPUT mangle rules
859 are required any more.
860
861 - added support of DPD restart mode
862
863 - ipsec starter now allows the use of wildcards in include
864 statements as e.g. in "include /etc/my_ipsec/*.conf".
865 Patch courtesy of Matthias Haas.
866
867 - the Netscape OID 'employeeNumber' is now recognized and can be
868 used as a Relative Distinguished Name in certificates.
869
870
871 strongswan-2.6.3
872 ----------------
873
874 - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec
875 command and not of ipsec setup any more.
876
877 - ipsec starter now supports AH authentication in conjunction with
878 ESP encryption. AH authentication is configured in ipsec.conf
879 via the auth=ah parameter.
880
881 - The command ipsec scencrypt|scdecrypt <args> is now an alias for
882 ipsec whack --scencrypt|scdecrypt <args>.
883
884 - get_sa_info() now determines for the native netkey IPsec stack
885 the exact time of the last use of an active eroute. This information
886 is used by the Dead Peer Detection algorithm and is also displayed by
887 the ipsec status command.
888
889
890 strongswan-2.6.2
891 ----------------
892
893 - running under the native Linux 2.6 IPsec stack, the function
894 get_sa_info() is called by ipsec auto --status to display the current
895 number of transmitted bytes per IPsec SA.
896
897 - get_sa_info() is also used by the Dead Peer Detection process to detect
898 recent ESP activity. If ESP traffic was received from the peer within
899 the last dpd_delay interval then no R_Y_THERE notification must be sent.
900
901 - strongSwan now supports the Relative Distinguished Name "unstructuredName"
902 in ID_DER_ASN1_DN identities. The following notations are possible:
903
904 rightid="unstructuredName=John Doe"
905 rightid="UN=John Doe"
906
907 - fixed a long-standing bug which caused PSK-based roadwarrior connections
908 to segfault in the function id.c:same_id() called by keys.c:get_secret()
909 if an FQDN, USER_FQDN, or Key ID was defined, as in the following example.
910
911 conn rw
912 right=%any
913 rightid=@foo.bar
914 authby=secret
915
916 - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall).
917
918 - ipsec starter didn't set host_addr and client.addr ports in whack msg.
919
920 - in order to guarantee backwards-compatibility with the script-based
921 auto function (e.g. auto --replace), the ipsec starter scripts stores
922 the defaultroute information in the temporary file /var/run/ipsec.info.
923
924 - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH
925 Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config
926 servers.
927
928 - the ipsec starter now also recognizes the parameters authby=never and
929 type=passthrough|pass|drop|reject.
930
931
932 strongswan-2.6.1
933 ----------------
934
935 - ipsec starter now supports the also parameter which allows
936 a modular structure of the connection definitions. Thus
937 "ipsec start" is now ready to replace "ipsec setup".
938
939
940 strongswan-2.6.0
941 ----------------
942
943 - Mathieu Lafon's popular ipsec starter tool has been added to the
944 strongSwan distribution. Many thanks go to Stephan Scholz from astaro
945 for his integration work. ipsec starter is a C program which is going
946 to replace the various shell and awk starter scripts (setup, _plutoload,
947 _plutostart, _realsetup, _startklips, _confread, and auto). Since
948 ipsec.conf is now parsed only once, the starting of multiple tunnels is
949 accelerated tremedously.
950
951 - Added support of %defaultroute to the ipsec starter. If the IP address
952 changes, a HUP signal to the ipsec starter will automatically
953 reload pluto's connections.
954
955 - moved most compile time configurations from pluto/Makefile to
956 Makefile.inc by defining the options USE_LIBCURL, USE_LDAP,
957 USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE.
958
959 - removed the ipsec verify and ipsec newhostkey commands
960
961 - fixed some 64-bit issues in formatted print statements
962
963 - The scepclient functionality implementing the Simple Certificate
964 Enrollment Protocol (SCEP) is nearly complete but hasn't been
965 documented yet.
966
967
968 strongswan-2.5.7
969 ----------------
970
971 - CA certicates are now automatically loaded from a smartcard
972 or USB crypto token and appear in the ipsec auto --listcacerts
973 listing.
974
975
976 strongswan-2.5.6
977 ----------------
978
979 - when using "ipsec whack --scencrypt <data>" with a PKCS#11
980 library that does not support the C_Encrypt() Cryptoki
981 function (e.g. OpenSC), the RSA encryption is done in
982 software using the public key fetched from the smartcard.
983
984 - The scepclient function now allows to define the
985 validity of a self-signed certificate using the --days,
986 --startdate, and --enddate options. The default validity
987 has been changed from one year to five years.
988
989
990 strongswan-2.5.5
991 ----------------
992
993 - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11
994 interface to other applications for RSA encryption and decryption
995 via the whack interface. Notation:
996
997 ipsec whack --scencrypt <data>
998 [--inbase 16|hex|64|base64|256|text|ascii]
999 [--outbase 16|hex|64|base64|256|text|ascii]
1000 [--keyid <keyid>]
1001
1002 ipsec whack --scdecrypt <data>
1003 [--inbase 16|hex|64|base64|256|text|ascii]
1004 [--outbase 16|hex|64|base64|256|text|ascii]
1005 [--keyid <keyid>]
1006
1007 The default setting for inbase and outbase is hex.
1008
1009 The new proxy interface can be used for securing symmetric
1010 encryption keys required by the cryptoloop or dm-crypt
1011 disk encryption schemes, especially in the case when
1012 pkcs11keepstate=yes causes pluto to lock the pkcs11 slot
1013 permanently.
1014
1015 - if the file /etc/ipsec.secrets is lacking during the startup of
1016 pluto then the root-readable file /etc/ipsec.d/private/myKey.der
1017 containing a 2048 bit RSA private key and a matching self-signed
1018 certificate stored in the file /etc/ipsec.d/certs/selfCert.der
1019 is automatically generated by calling the function
1020
1021 ipsec scepclient --out pkcs1 --out cert-self
1022
1023 scepclient was written by Jan Hutter and Martin Willi, students
1024 at the University of Applied Sciences in Rapperswil, Switzerland.
1025
1026
1027 strongswan-2.5.4
1028 ----------------
1029
1030 - the current extension of the PKCS#7 framework introduced
1031 a parsing error in PKCS#7 wrapped X.509 certificates that are
1032 e.g. transmitted by Windows XP when multi-level CAs are used.
1033 the parsing syntax has been fixed.
1034
1035 - added a patch by Gerald Richter which tolerates multiple occurrences
1036 of the ipsec0 interface when using KLIPS.
1037
1038
1039 strongswan-2.5.3
1040 ----------------
1041
1042 - with gawk-3.1.4 the word "default2 has become a protected
1043 keyword for use in switch statements and cannot be used any
1044 more in the strongSwan scripts. This problem has been
1045 solved by renaming "default" to "defaults" and "setdefault"
1046 in the scripts _confread and auto, respectively.
1047
1048 - introduced the parameter leftsendcert with the values
1049
1050 always|yes (the default, always send a cert)
1051 ifasked (send the cert only upon a cert request)
1052 never|no (never send a cert, used for raw RSA keys and
1053 self-signed certs)
1054
1055 - fixed the initialization of the ESP key length to a default of
1056 128 bits in the case that the peer does not send a key length
1057 attribute for AES encryption.
1058
1059 - applied Herbert Xu's uniqueIDs patch
1060
1061 - applied Herbert Xu's CLOEXEC patches
1062
1063
1064 strongswan-2.5.2
1065 ----------------
1066
1067 - CRLs can now be cached also in the case when the issuer's
1068 certificate does not contain a subjectKeyIdentifier field.
1069 In that case the subjectKeyIdentifier is computed by pluto as the
1070 160 bit SHA-1 hash of the issuer's public key in compliance
1071 with section 4.2.1.2 of RFC 3280.
1072
1073 - Fixed a bug introduced by strongswan-2.5.1 which eliminated
1074 not only multiple Quick Modes of a given connection but also
1075 multiple connections between two security gateways.
1076
1077
1078 strongswan-2.5.1
1079 ----------------
1080
1081 - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute
1082 installed either by setting auto=route in ipsec.conf or by
1083 a connection put into hold, generates an XFRM_AQUIRE event
1084 for each packet that wants to use the not-yet exisiting
1085 tunnel. Up to now each XFRM_AQUIRE event led to an entry in
1086 the Quick Mode queue, causing multiple IPsec SA to be
1087 established in rapid succession. Starting with strongswan-2.5.1
1088 only a single IPsec SA is established per host-pair connection.
1089
1090 - Right after loading the PKCS#11 module, all smartcard slots are
1091 searched for certificates. The result can be viewed using
1092 the command
1093
1094 ipsec auto --listcards
1095
1096 The certificate objects found in the slots are numbered
1097 starting with #1, #2, etc. This position number can be used to address
1098 certificates (leftcert=%smartcard) and keys (: PIN %smartcard)
1099 in ipsec.conf and ipsec.secrets, respectively:
1100
1101 %smartcard (selects object #1)
1102 %smartcard#1 (selects object #1)
1103 %smartcard#3 (selects object #3)
1104
1105 As an alternative the existing retrieval scheme can be used:
1106
1107 %smartcard:45 (selects object with id=45)
1108 %smartcard0 (selects first object in slot 0)
1109 %smartcard4:45 (selects object in slot 4 with id=45)
1110
1111 - Depending on the settings of CKA_SIGN and CKA_DECRYPT
1112 private key flags either C_Sign() or C_Decrypt() is used
1113 to generate a signature.
1114
1115 - The output buffer length parameter siglen in C_Sign()
1116 is now initialized to the actual size of the output
1117 buffer prior to the function call. This fixes the
1118 CKR_BUFFER_TOO_SMALL error that could occur when using
1119 the OpenSC PKCS#11 module.
1120
1121 - Changed the initialization of the PKCS#11 CK_MECHANISM in
1122 C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }.
1123
1124 - Refactored the RSA public/private key code and transferred it
1125 from keys.c to the new pkcs1.c file as a preparatory step
1126 towards the release of the SCEP client.
1127
1128
1129 strongswan-2.5.0
1130 ----------------
1131
1132 - The loading of a PKCS#11 smartcard library module during
1133 runtime does not require OpenSC library functions any more
1134 because the corresponding code has been integrated into
1135 smartcard.c. Also the RSAREF pkcs11 header files have been
1136 included in a newly created pluto/rsaref directory so that
1137 no external include path has to be defined any longer.
1138
1139 - A long-awaited feature has been implemented at last:
1140 The local caching of CRLs fetched via HTTP or LDAP, activated
1141 by the parameter cachecrls=yes in the config setup section
1142 of ipsec.conf. The dynamically fetched CRLs are stored under
1143 a unique file name containing the issuer's subjectKeyID
1144 in /etc/ipsec.d/crls.
1145
1146 - Applied a one-line patch courtesy of Michael Richardson
1147 from the Openswan project which fixes the kernel-oops
1148 in KLIPS when an snmp daemon is running on the same box.
1149
1150
1151 strongswan-2.4.4
1152 ----------------
1153
1154 - Eliminated null length CRL distribution point strings.
1155
1156 - Fixed a trust path evaluation bug introduced with 2.4.3
1157
1158
1159 strongswan-2.4.3
1160 ----------------
1161
1162 - Improved the joint OCSP / CRL revocation policy.
1163 OCSP responses have precedence over CRL entries.
1164
1165 - Introduced support of CRLv2 reason codes.
1166
1167 - Fixed a bug with key-pad equipped readers which caused
1168 pluto to prompt for the pin via the console when the first
1169 occasion to enter the pin via the key-pad was missed.
1170
1171 - When pluto is built with LDAP_V3 enabled, the library
1172 liblber required by newer versions of openldap is now
1173 included.
1174
1175
1176 strongswan-2.4.2
1177 ----------------
1178
1179 - Added the _updown_espmark template which requires all
1180 incoming ESP traffic to be marked with a default mark
1181 value of 50.
1182
1183 - Introduced the pkcs11keepstate parameter in the config setup
1184 section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11
1185 session and login states are kept as long as possible during
1186 the lifetime of pluto. This means that a PIN entry via a key
1187 pad has to be done only once.
1188
1189 - Introduced the pkcs11module parameter in the config setup
1190 section of ipsec.conf which specifies the PKCS#11 module
1191 to be used with smart cards. Example:
1192
1193 pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo
1194
1195 - Added support of smartcard readers equipped with a PIN pad.
1196
1197 - Added patch by Jay Pfeifer which detects when netkey
1198 modules have been statically built into the Linux 2.6 kernel.
1199
1200 - Added two patches by Herbert Xu. The first uses ip xfrm
1201 instead of setkey to flush the IPsec policy database. The
1202 second sets the optional flag in inbound IPComp SAs only.
1203
1204 - Applied Ulrich Weber's patch which fixes an interoperability
1205 problem between native IPsec and KLIPS systems caused by
1206 setting the replay window to 32 instead of 0 for ipcomp.
1207
1208
1209 strongswan-2.4.1
1210 ----------------
1211
1212 - Fixed a bug which caused an unwanted Mode Config request
1213 to be initiated in the case where "right" was used to denote
1214 the local side in ipsec.conf and "left" the remote side,
1215 contrary to the recommendation that "right" be remote and
1216 "left" be"local".
1217
1218
1219 strongswan-2.4.0a
1220 -----------------
1221
1222 - updated Vendor ID to strongSwan-2.4.0
1223
1224 - updated copyright statement to include David Buechi and
1225 Michael Meier
1226
1227
1228 strongswan-2.4.0
1229 ----------------
1230
1231 - strongSwan now communicates with attached smartcards and
1232 USB crypto tokens via the standardized PKCS #11 interface.
1233 By default the OpenSC library from www.opensc.org is used
1234 but any other PKCS#11 library could be dynamically linked.
1235 strongSwan's PKCS#11 API was implemented by David Buechi
1236 and Michael Meier, both graduates of the Zurich University
1237 of Applied Sciences in Winterthur, Switzerland.
1238
1239 - When a %trap eroute is triggered by an outgoing IP packet
1240 then the native IPsec stack of the Linux 2.6 kernel [often/
1241 always?] returns an XFRM_ACQUIRE message with an undefined
1242 protocol family field and the connection setup fails.
1243 As a workaround IPv4 (AF_INET) is now assumed.
1244
1245 - the results of the UML test scenarios are now enhanced
1246 with block diagrams of the virtual network topology used
1247 in a particular test.
1248
1249
1250 strongswan-2.3.2
1251 ----------------
1252
1253 - fixed IV used to decrypt informational messages.
1254 This bug was introduced with Mode Config functionality.
1255
1256 - fixed NCP Vendor ID.
1257
1258 - undid one of Ulrich Weber's maximum udp size patches
1259 because it caused a segmentation fault with NAT-ed
1260 Delete SA messages.
1261
1262 - added UML scenarios wildcards and attr-cert which
1263 demonstrate the implementation of IPsec policies based
1264 on wildcard parameters contained in Distinguished Names and
1265 on X.509 attribute certificates, respectively.
1266
1267
1268 strongswan-2.3.1
1269 ----------------
1270
1271 - Added basic Mode Config functionality
1272
1273 - Added Mathieu Lafon's patch which upgrades the status of
1274 the NAT-Traversal implementation to RFC 3947.
1275
1276 - The _startklips script now also loads the xfrm4_tunnel
1277 module.
1278
1279 - Added Ulrich Weber's netlink replay window size and
1280 maximum udp size patches.
1281
1282 - UML testing now uses the Linux 2.6.10 UML kernel by default.
1283
1284
1285 strongswan-2.3.0
1286 ----------------
1287
1288 - Eric Marchionni and Patrik Rayo, both recent graduates from
1289 the Zuercher Hochschule Winterthur in Switzerland, created a
1290 User-Mode-Linux test setup for strongSwan. For more details
1291 please read the INSTALL and README documents in the testing
1292 subdirectory.
1293
1294 - Full support of group attributes based on X.509 attribute
1295 certificates. Attribute certificates can be generated
1296 using the openac facility. For more details see
1297
1298 man ipsec_openac.
1299
1300 The group attributes can be used in connection definitions
1301 in order to give IPsec access to specific user groups.
1302 This is done with the new parameter left|rightgroups as in
1303
1304 rightgroups="Research, Sales"
1305
1306 giving access to users possessing the group attributes
1307 Research or Sales, only.
1308
1309 - In Quick Mode clients with subnet mask /32 are now
1310 coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should
1311 fix rekeying problems with the SafeNet/SoftRemote and NCP
1312 Secure Entry Clients.
1313
1314 - Changed the defaults of the ikelifetime and keylife parameters
1315 to 3h and 1h, respectively. The maximum allowable values are
1316 now both set to 24 h.
1317
1318 - Suppressed notification wars between two IPsec peers that
1319 could e.g. be triggered by incorrect ISAKMP encryption.
1320
1321 - Public RSA keys can now have identical IDs if either the
1322 issuing CA or the serial number is different. The serial
1323 number of a certificate is now shown by the command
1324
1325 ipsec auto --listpubkeys
1326
1327
1328 strongswan-2.2.2
1329 ----------------
1330
1331 - Added Tuomo Soini's sourceip feature which allows a strongSwan
1332 roadwarrior to use a fixed Virtual IP (see README section 2.6)
1333 and reduces the well-known four tunnel case on VPN gateways to
1334 a single tunnel definition (see README section 2.4).
1335
1336 - Fixed a bug occuring with NAT-Traversal enabled when the responder
1337 suddenly turns initiator and the initiator cannot find a matching
1338 connection because of the floated IKE port 4500.
1339
1340 - Removed misleading ipsec verify command from barf.
1341
1342 - Running under the native IP stack, ipsec --version now shows
1343 the Linux kernel version (courtesy to the Openswan project).
1344
1345
1346 strongswan-2.2.1
1347 ----------------
1348
1349 - Introduced the ipsec auto --listalgs monitoring command which lists
1350 all currently registered IKE and ESP algorithms.
1351
1352 - Fixed a bug in the ESP algorithm selection occuring when the strict flag
1353 is set and the first proposed transform does not match.
1354
1355 - Fixed another deadlock in the use of the lock_certs_and_keys() mutex,
1356 occuring when a smartcard is present.
1357
1358 - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event.
1359
1360 - Fixed the printing of the notification names (null)
1361
1362 - Applied another of Herbert Xu's Netlink patches.
1363
1364
1365 strongswan-2.2.0
1366 ----------------
1367
1368 - Support of Dead Peer Detection. The connection parameter
1369
1370 dpdaction=clear|hold
1371
1372 activates DPD for the given connection.
1373
1374 - The default Opportunistic Encryption (OE) policy groups are not
1375 automatically included anymore. Those wishing to activate OE can include
1376 the policy group with the following statement in ipsec.conf:
1377
1378 include /etc/ipsec.d/examples/oe.conf
1379
1380 The default for [right|left]rsasigkey is now set to %cert.
1381
1382 - strongSwan now has a Vendor ID of its own which can be activated
1383 using the compile option VENDORID
1384
1385 - Applied Herbert Xu's patch which sets the compression algorithm correctly.
1386
1387 - Applied Herbert Xu's patch fixing an ESPINUDP problem
1388
1389 - Applied Herbert Xu's patch setting source/destination port numbers.
1390
1391 - Reapplied one of Herbert Xu's NAT-Traversal patches which got
1392 lost during the migration from SuperFreeS/WAN.
1393
1394 - Fixed a deadlock in the use of the lock_certs_and_keys() mutex.
1395
1396 - Fixed the unsharing of alg parameters when instantiating group
1397 connection.
1398
1399
1400 strongswan-2.1.5
1401 ----------------
1402
1403 - Thomas Walpuski made me aware of a potential DoS attack via
1404 a PKCS#7-wrapped certificate bundle which could overwrite valid CA
1405 certificates in Pluto's authority certificate store. This vulnerability
1406 was fixed by establishing trust in CA candidate certificates up to a
1407 trusted root CA prior to insertion into Pluto's chained list.
1408
1409 - replaced the --assign option by the -v option in the auto awk script
1410 in order to make it run with mawk under debian/woody.
1411
1412
1413 strongswan-2.1.4
1414 ----------------
1415
1416 - Split of the status information between ipsec auto --status (concise)
1417 and ipsec auto --statusall (verbose). Both commands can be used with
1418 an optional connection selector:
1419
1420 ipsec auto --status[all] <connection_name>
1421
1422 - Added the description of X.509 related features to the ipsec_auto(8)
1423 man page.
1424
1425 - Hardened the ASN.1 parser in debug mode, especially the printing
1426 of malformed distinguished names.
1427
1428 - The size of an RSA public key received in a certificate is now restricted to
1429
1430 512 bits <= modulus length <= 8192 bits.
1431
1432 - Fixed the debug mode enumeration.
1433
1434
1435 strongswan-2.1.3
1436 ----------------
1437
1438 - Fixed another PKCS#7 vulnerability which could lead to an
1439 endless loop while following the X.509 trust chain.
1440
1441
1442 strongswan-2.1.2
1443 ----------------
1444
1445 - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski
1446 that accepted end certificates having identical issuer and subject
1447 distinguished names in a multi-tier X.509 trust chain.
1448
1449
1450 strongswan-2.1.1
1451 ----------------
1452
1453 - Removed all remaining references to ipsec_netlink.h in KLIPS.
1454
1455
1456 strongswan-2.1.0
1457 ----------------
1458
1459 - The new "ca" section allows to define the following parameters:
1460
1461 ca kool
1462 cacert=koolCA.pem # cacert of kool CA
1463 ocspuri=http://ocsp.kool.net:8001 # ocsp server
1464 ldapserver=ldap.kool.net # default ldap server
1465 crluri=http://www.kool.net/kool.crl # crl distribution point
1466 crluri2="ldap:///O=Kool, C= .." # crl distribution point #2
1467 auto=add # add, ignore
1468
1469 The ca definitions can be monitored via the command
1470
1471 ipsec auto --listcainfos
1472
1473 - Fixed cosmetic corruption of /proc filesystem by integrating
1474 D. Hugh Redelmeier's freeswan-2.06 kernel fixes.
1475
1476
1477 strongswan-2.0.2
1478 ----------------
1479
1480 - Added support for the 818043 NAT-Traversal update of Microsoft's
1481 Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode.
1482
1483 - A symbolic link to libcrypto is now added in the kernel sources
1484 during kernel compilation
1485
1486 - Fixed a couple of 64 bit issues (mostly casts to int).
1487 Thanks to Ken Bantoft who checked my sources on a 64 bit platform.
1488
1489 - Replaced s[n]printf() statements in the kernel by ipsec_snprintf().
1490 Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro
1491 of the FreeS/WAN team who solved this problem with the 2.4.25 kernel.
1492
1493
1494 strongswan-2.0.1
1495 ----------------
1496
1497 - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName
1498 certificate extension which contains no generalName item) can cause
1499 a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has
1500 been hardened to make it more robust against malformed ASN.1 objects.
1501
1502 - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native
1503 Linux 2.6 IPsec stack.
1504
1505
1506 strongswan-2.0.0
1507 ----------------
1508
1509 - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12