]>
Commit | Line | Data |
---|---|---|
1 | strongswan-4.0.5 | |
2 | ---------------- | |
3 | ||
4 | - IKEv1: Implementation of ModeConfig push mode via the new connection | |
5 | keyword modeconfig=push allows interoperability with Cisco VPN gateways. | |
6 | ||
7 | - IKEv1: The command ipsec statusall now shows "DPD active" for all | |
8 | ISAKMP SAs that are under active Dead Peer Detection control. | |
9 | ||
10 | - IKEv2: Charon's logging and debugging framework has been completely rewritten. | |
11 | Instead of logger, special printf() functions are used to directly | |
12 | print objects like hosts (%H) identifications (%D), certificates (%Q), | |
13 | etc. The number of debugging levels have been reduced to: | |
14 | ||
15 | 0 (audit), 1 (control), 2 (controlmore), 3 (raw), 4 (private) | |
16 | ||
17 | The debugging levels can either be specified statically in ipsec.conf as | |
18 | ||
19 | config setup | |
20 | charondebug="lib 1, cfg 3, net 2" | |
21 | ||
22 | or changed at runtime via stroke as | |
23 | ||
24 | ipsec stroke loglevel cfg 2 | |
25 | ||
26 | ||
27 | strongswan-4.0.4 | |
28 | ---------------- | |
29 | ||
30 | - Implemented full support for IPv6-in-IPv6 tunnels. | |
31 | ||
32 | - Added configuration options for dead peer detection in IKEv2. dpd_action | |
33 | types "clear", "hold" and "restart" are supported. The dpd_timeout | |
34 | value is not used, as the normal retransmission policy applies to | |
35 | detect dead peers. The dpd_delay parameter enables sending of empty | |
36 | informational message to detect dead peers in case of inactivity. | |
37 | ||
38 | - Added support for preshared keys in IKEv2. PSK keys configured in | |
39 | ipsec.secrets are loaded. The authby parameter specifies the authentication | |
40 | method to authentificate ourself, the other peer may use PSK or RSA. | |
41 | ||
42 | - Changed retransmission policy to respect the keyingtries parameter. | |
43 | ||
44 | - Added private key decryption. PEM keys encrypted with AES-128/192/256 | |
45 | or 3DES are supported. | |
46 | ||
47 | - Implemented DES/3DES algorithms in libstrongswan. 3DES can be used to | |
48 | encrypt IKE traffic. | |
49 | ||
50 | - Implemented SHA-256/384/512 in libstrongswan, allows usage of certificates | |
51 | signed with such a hash algorithm. | |
52 | ||
53 | - Added initial support for updown scripts. The actions up-host/client and | |
54 | down-host/client are executed. The leftfirewall=yes parameter | |
55 | uses the default updown script to insert dynamic firewall rules, a custom | |
56 | updown script may be specified with the leftupdown parameter. | |
57 | ||
58 | ||
59 | strongswan-4.0.3 | |
60 | ---------------- | |
61 | ||
62 | - Added support for the auto=route ipsec.conf parameter and the | |
63 | ipsec route/unroute commands for IKEv2. This allows to set up IKE_SAs and | |
64 | CHILD_SAs dynamically on demand when traffic is detected by the | |
65 | kernel. | |
66 | ||
67 | - Added support for rekeying IKE_SAs in IKEv2 using the ikelifetime parameter. | |
68 | As specified in IKEv2, no reauthentication is done (unlike in IKEv1), only | |
69 | new keys are generated using perfect forward secrecy. An optional flag | |
70 | which enforces reauthentication will be implemented later. | |
71 | ||
72 | - "sha" and "sha1" are now treated as synonyms in the ike= and esp= | |
73 | algorithm configuration statements. | |
74 | ||
75 | ||
76 | strongswan-4.0.2 | |
77 | ---------------- | |
78 | ||
79 | - Full X.509 certificate trust chain verification has been implemented. | |
80 | End entity certificates can be exchanged via CERT payloads. The current | |
81 | default is leftsendcert=always, since CERTREQ payloads are not supported | |
82 | yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls. | |
83 | ||
84 | - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2 | |
85 | would offer more possibilities for traffic selection, but the Linux kernel | |
86 | currently does not support it. That's why we stick with these simple | |
87 | ipsec.conf rules for now. | |
88 | ||
89 | - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no | |
90 | IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear, | |
91 | dpddelay=60s). | |
92 | ||
93 | - Initial NAT traversal support in IKEv2. Charon includes NAT detection | |
94 | notify payloads to detect NAT routers between the peers. It switches | |
95 | to port 4500, uses UDP encapsulated ESP packets, handles peer address | |
96 | changes gracefully and sends keep alive message periodically. | |
97 | ||
98 | - Reimplemented IKE_SA state machine for charon, which allows simultaneous | |
99 | rekeying, more shared code, cleaner design, proper retransmission | |
100 | and a more extensible code base. | |
101 | ||
102 | - The mixed PSK/RSA roadwarrior detection capability introduced by the | |
103 | strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal | |
104 | payloads by the responder right before any defined IKE Main Mode state had | |
105 | been established. Although any form of bad proposal syntax was being correctly | |
106 | detected by the payload parser, the subsequent error handler didn't check | |
107 | the state pointer before logging current state information, causing an | |
108 | immediate crash of the pluto keying daemon due to a NULL pointer. | |
109 | ||
110 | ||
111 | strongswan-4.0.1 | |
112 | ---------------- | |
113 | ||
114 | - Added algorithm selection to charon: New default algorithms for | |
115 | ike=aes128-sha-modp2048, as both daemons support it. The default | |
116 | for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles | |
117 | the ike/esp parameter the same way as pluto. As this syntax does | |
118 | not allow specification of a pseudo random function, the same | |
119 | algorithm as for integrity is used (currently sha/md5). Supported | |
120 | algorithms for IKE: | |
121 | Encryption: aes128, aes192, aes256 | |
122 | Integrity/PRF: md5, sha (using hmac) | |
123 | DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192 | |
124 | and for ESP: | |
125 | Encryption: aes128, aes192, aes256, 3des, blowfish128, | |
126 | blowfish192, blowfish256 | |
127 | Integrity: md5, sha1 | |
128 | More IKE encryption algorithms will come after porting libcrypto into | |
129 | libstrongswan. | |
130 | ||
131 | - initial support for rekeying CHILD_SAs using IKEv2. Currently no | |
132 | perfect forward secrecy is used. The rekeying parameters rekey, | |
133 | rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported | |
134 | when using IKEv2. WARNING: charon currently is unable to handle | |
135 | simultaneous rekeying. To avoid such a situation, use a large | |
136 | rekeyfuzz, or even better, set rekey=no on one peer. | |
137 | ||
138 | - support for host2host, net2net, host2net (roadwarrior) tunnels | |
139 | using predefined RSA certificates (see uml scenarios for | |
140 | configuration examples). | |
141 | ||
142 | - new build environment featuring autotools. Features such | |
143 | as HTTP, LDAP and smartcard support may be enabled using | |
144 | the ./configure script. Changing install directories | |
145 | is possible, too. See ./configure --help for more details. | |
146 | ||
147 | - better integration of charon with ipsec starter, which allows | |
148 | (almost) transparent operation with both daemons. charon | |
149 | handles ipsec commands up, down, status, statusall, listall, | |
150 | listcerts and allows proper load, reload and delete of connections | |
151 | via ipsec starter. | |
152 | ||
153 | ||
154 | strongswan-4.0.0 | |
155 | ---------------- | |
156 | ||
157 | - initial support of the IKEv2 protocol. Connections in | |
158 | ipsec.conf designated by keyexchange=ikev2 are negotiated | |
159 | by the new IKEv2 charon keying daemon whereas those marked | |
160 | by keyexchange=ikev1 or the default keyexchange=ike are | |
161 | handled thy the IKEv1 pluto keying daemon. Currently only | |
162 | a limited subset of functions are available with IKEv2 | |
163 | (Default AES encryption, authentication based on locally | |
164 | imported X.509 certificates, unencrypted private RSA keys | |
165 | in PKCS#1 file format, limited functionality of the ipsec | |
166 | status command). | |
167 | ||
168 | ||
169 | strongswan-2.7.0 | |
170 | ---------------- | |
171 | ||
172 | - the dynamic iptables rules from the _updown_x509 template | |
173 | for KLIPS and the _updown_policy template for NETKEY have | |
174 | been merged into the default _updown script. The existing | |
175 | left|rightfirewall keyword causes the automatic insertion | |
176 | and deletion of ACCEPT rules for tunneled traffic upon | |
177 | the successful setup and teardown of an IPsec SA, respectively. | |
178 | left|rightfirwall can be used with KLIPS under any Linux 2.4 | |
179 | kernel or with NETKEY under a Linux kernel version >= 2.6.16 | |
180 | in conjuction with iptables >= 1.3.5. For NETKEY under a Linux | |
181 | kernel version < 2.6.16 which does not support IPsec policy | |
182 | matching yet, please continue to use a copy of the _updown_espmark | |
183 | template loaded via the left|rightupdown keyword. | |
184 | ||
185 | - a new left|righthostaccess keyword has been introduced which | |
186 | can be used in conjunction with left|rightfirewall and the | |
187 | default _updown script. By default leftfirewall=yes inserts | |
188 | a bi-directional iptables FORWARD rule for a local client network | |
189 | with a netmask different from 255.255.255.255 (single host). | |
190 | This does not allow to access the VPN gateway host via its | |
191 | internal network interface which is part of the client subnet | |
192 | because an iptables INPUT and OUTPUT rule would be required. | |
193 | lefthostaccess=yes will cause this additional ACCEPT rules to | |
194 | be inserted. | |
195 | ||
196 | - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal | |
197 | payload is preparsed in order to find out whether the roadwarrior | |
198 | requests PSK or RSA so that a matching connection candidate can | |
199 | be found. | |
200 | ||
201 | ||
202 | strongswan-2.6.4 | |
203 | ---------------- | |
204 | ||
205 | - the new _updown_policy template allows ipsec policy based | |
206 | iptables firewall rules. Required are iptables version | |
207 | >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes | |
208 | the _updown_espmark template, so that no INPUT mangle rules | |
209 | are required any more. | |
210 | ||
211 | - added support of DPD restart mode | |
212 | ||
213 | - ipsec starter now allows the use of wildcards in include | |
214 | statements as e.g. in "include /etc/my_ipsec/*.conf". | |
215 | Patch courtesy of Matthias Haas. | |
216 | ||
217 | - the Netscape OID 'employeeNumber' is now recognized and can be | |
218 | used as a Relative Distinguished Name in certificates. | |
219 | ||
220 | ||
221 | strongswan-2.6.3 | |
222 | ---------------- | |
223 | ||
224 | - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec | |
225 | command and not of ipsec setup any more. | |
226 | ||
227 | - ipsec starter now supports AH authentication in conjunction with | |
228 | ESP encryption. AH authentication is configured in ipsec.conf | |
229 | via the auth=ah parameter. | |
230 | ||
231 | - The command ipsec scencrypt|scdecrypt <args> is now an alias for | |
232 | ipsec whack --scencrypt|scdecrypt <args>. | |
233 | ||
234 | - get_sa_info() now determines for the native netkey IPsec stack | |
235 | the exact time of the last use of an active eroute. This information | |
236 | is used by the Dead Peer Detection algorithm and is also displayed by | |
237 | the ipsec status command. | |
238 | ||
239 | ||
240 | strongswan-2.6.2 | |
241 | ---------------- | |
242 | ||
243 | - running under the native Linux 2.6 IPsec stack, the function | |
244 | get_sa_info() is called by ipsec auto --status to display the current | |
245 | number of transmitted bytes per IPsec SA. | |
246 | ||
247 | - get_sa_info() is also used by the Dead Peer Detection process to detect | |
248 | recent ESP activity. If ESP traffic was received from the peer within | |
249 | the last dpd_delay interval then no R_Y_THERE notification must be sent. | |
250 | ||
251 | - strongSwan now supports the Relative Distinguished Name "unstructuredName" | |
252 | in ID_DER_ASN1_DN identities. The following notations are possible: | |
253 | ||
254 | rightid="unstructuredName=John Doe" | |
255 | rightid="UN=John Doe" | |
256 | ||
257 | - fixed a long-standing bug which caused PSK-based roadwarrior connections | |
258 | to segfault in the function id.c:same_id() called by keys.c:get_secret() | |
259 | if an FQDN, USER_FQDN, or Key ID was defined, as in the following example. | |
260 | ||
261 | conn rw | |
262 | right=%any | |
263 | rightid=@foo.bar | |
264 | authby=secret | |
265 | ||
266 | - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall). | |
267 | ||
268 | - ipsec starter didn't set host_addr and client.addr ports in whack msg. | |
269 | ||
270 | - in order to guarantee backwards-compatibility with the script-based | |
271 | auto function (e.g. auto --replace), the ipsec starter scripts stores | |
272 | the defaultroute information in the temporary file /var/run/ipsec.info. | |
273 | ||
274 | - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH | |
275 | Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config | |
276 | servers. | |
277 | ||
278 | - the ipsec starter now also recognizes the parameters authby=never and | |
279 | type=passthrough|pass|drop|reject. | |
280 | ||
281 | ||
282 | strongswan-2.6.1 | |
283 | ---------------- | |
284 | ||
285 | - ipsec starter now supports the also parameter which allows | |
286 | a modular structure of the connection definitions. Thus | |
287 | "ipsec start" is now ready to replace "ipsec setup". | |
288 | ||
289 | ||
290 | strongswan-2.6.0 | |
291 | ---------------- | |
292 | ||
293 | - Mathieu Lafon's popular ipsec starter tool has been added to the | |
294 | strongSwan distribution. Many thanks go to Stephan Scholz from astaro | |
295 | for his integration work. ipsec starter is a C program which is going | |
296 | to replace the various shell and awk starter scripts (setup, _plutoload, | |
297 | _plutostart, _realsetup, _startklips, _confread, and auto). Since | |
298 | ipsec.conf is now parsed only once, the starting of multiple tunnels is | |
299 | accelerated tremedously. | |
300 | ||
301 | - Added support of %defaultroute to the ipsec starter. If the IP address | |
302 | changes, a HUP signal to the ipsec starter will automatically | |
303 | reload pluto's connections. | |
304 | ||
305 | - moved most compile time configurations from pluto/Makefile to | |
306 | Makefile.inc by defining the options USE_LIBCURL, USE_LDAP, | |
307 | USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE. | |
308 | ||
309 | - removed the ipsec verify and ipsec newhostkey commands | |
310 | ||
311 | - fixed some 64-bit issues in formatted print statements | |
312 | ||
313 | - The scepclient functionality implementing the Simple Certificate | |
314 | Enrollment Protocol (SCEP) is nearly complete but hasn't been | |
315 | documented yet. | |
316 | ||
317 | ||
318 | strongswan-2.5.7 | |
319 | ---------------- | |
320 | ||
321 | - CA certicates are now automatically loaded from a smartcard | |
322 | or USB crypto token and appear in the ipsec auto --listcacerts | |
323 | listing. | |
324 | ||
325 | ||
326 | strongswan-2.5.6 | |
327 | ---------------- | |
328 | ||
329 | - when using "ipsec whack --scencrypt <data>" with a PKCS#11 | |
330 | library that does not support the C_Encrypt() Cryptoki | |
331 | function (e.g. OpenSC), the RSA encryption is done in | |
332 | software using the public key fetched from the smartcard. | |
333 | ||
334 | - The scepclient function now allows to define the | |
335 | validity of a self-signed certificate using the --days, | |
336 | --startdate, and --enddate options. The default validity | |
337 | has been changed from one year to five years. | |
338 | ||
339 | ||
340 | strongswan-2.5.5 | |
341 | ---------------- | |
342 | ||
343 | - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11 | |
344 | interface to other applications for RSA encryption and decryption | |
345 | via the whack interface. Notation: | |
346 | ||
347 | ipsec whack --scencrypt <data> | |
348 | [--inbase 16|hex|64|base64|256|text|ascii] | |
349 | [--outbase 16|hex|64|base64|256|text|ascii] | |
350 | [--keyid <keyid>] | |
351 | ||
352 | ipsec whack --scdecrypt <data> | |
353 | [--inbase 16|hex|64|base64|256|text|ascii] | |
354 | [--outbase 16|hex|64|base64|256|text|ascii] | |
355 | [--keyid <keyid>] | |
356 | ||
357 | The default setting for inbase and outbase is hex. | |
358 | ||
359 | The new proxy interface can be used for securing symmetric | |
360 | encryption keys required by the cryptoloop or dm-crypt | |
361 | disk encryption schemes, especially in the case when | |
362 | pkcs11keepstate=yes causes pluto to lock the pkcs11 slot | |
363 | permanently. | |
364 | ||
365 | - if the file /etc/ipsec.secrets is lacking during the startup of | |
366 | pluto then the root-readable file /etc/ipsec.d/private/myKey.der | |
367 | containing a 2048 bit RSA private key and a matching self-signed | |
368 | certificate stored in the file /etc/ipsec.d/certs/selfCert.der | |
369 | is automatically generated by calling the function | |
370 | ||
371 | ipsec scepclient --out pkcs1 --out cert-self | |
372 | ||
373 | scepclient was written by Jan Hutter and Martin Willi, students | |
374 | at the University of Applied Sciences in Rapperswil, Switzerland. | |
375 | ||
376 | ||
377 | strongswan-2.5.4 | |
378 | ---------------- | |
379 | ||
380 | - the current extension of the PKCS#7 framework introduced | |
381 | a parsing error in PKCS#7 wrapped X.509 certificates that are | |
382 | e.g. transmitted by Windows XP when multi-level CAs are used. | |
383 | the parsing syntax has been fixed. | |
384 | ||
385 | - added a patch by Gerald Richter which tolerates multiple occurrences | |
386 | of the ipsec0 interface when using KLIPS. | |
387 | ||
388 | ||
389 | strongswan-2.5.3 | |
390 | ---------------- | |
391 | ||
392 | - with gawk-3.1.4 the word "default2 has become a protected | |
393 | keyword for use in switch statements and cannot be used any | |
394 | more in the strongSwan scripts. This problem has been | |
395 | solved by renaming "default" to "defaults" and "setdefault" | |
396 | in the scripts _confread and auto, respectively. | |
397 | ||
398 | - introduced the parameter leftsendcert with the values | |
399 | ||
400 | always|yes (the default, always send a cert) | |
401 | ifasked (send the cert only upon a cert request) | |
402 | never|no (never send a cert, used for raw RSA keys and | |
403 | self-signed certs) | |
404 | ||
405 | - fixed the initialization of the ESP key length to a default of | |
406 | 128 bits in the case that the peer does not send a key length | |
407 | attribute for AES encryption. | |
408 | ||
409 | - applied Herbert Xu's uniqueIDs patch | |
410 | ||
411 | - applied Herbert Xu's CLOEXEC patches | |
412 | ||
413 | ||
414 | strongswan-2.5.2 | |
415 | ---------------- | |
416 | ||
417 | - CRLs can now be cached also in the case when the issuer's | |
418 | certificate does not contain a subjectKeyIdentifier field. | |
419 | In that case the subjectKeyIdentifier is computed by pluto as the | |
420 | 160 bit SHA-1 hash of the issuer's public key in compliance | |
421 | with section 4.2.1.2 of RFC 3280. | |
422 | ||
423 | - Fixed a bug introduced by strongswan-2.5.1 which eliminated | |
424 | not only multiple Quick Modes of a given connection but also | |
425 | multiple connections between two security gateways. | |
426 | ||
427 | ||
428 | strongswan-2.5.1 | |
429 | ---------------- | |
430 | ||
431 | - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute | |
432 | installed either by setting auto=route in ipsec.conf or by | |
433 | a connection put into hold, generates an XFRM_AQUIRE event | |
434 | for each packet that wants to use the not-yet exisiting | |
435 | tunnel. Up to now each XFRM_AQUIRE event led to an entry in | |
436 | the Quick Mode queue, causing multiple IPsec SA to be | |
437 | established in rapid succession. Starting with strongswan-2.5.1 | |
438 | only a single IPsec SA is established per host-pair connection. | |
439 | ||
440 | - Right after loading the PKCS#11 module, all smartcard slots are | |
441 | searched for certificates. The result can be viewed using | |
442 | the command | |
443 | ||
444 | ipsec auto --listcards | |
445 | ||
446 | The certificate objects found in the slots are numbered | |
447 | starting with #1, #2, etc. This position number can be used to address | |
448 | certificates (leftcert=%smartcard) and keys (: PIN %smartcard) | |
449 | in ipsec.conf and ipsec.secrets, respectively: | |
450 | ||
451 | %smartcard (selects object #1) | |
452 | %smartcard#1 (selects object #1) | |
453 | %smartcard#3 (selects object #3) | |
454 | ||
455 | As an alternative the existing retrieval scheme can be used: | |
456 | ||
457 | %smartcard:45 (selects object with id=45) | |
458 | %smartcard0 (selects first object in slot 0) | |
459 | %smartcard4:45 (selects object in slot 4 with id=45) | |
460 | ||
461 | - Depending on the settings of CKA_SIGN and CKA_DECRYPT | |
462 | private key flags either C_Sign() or C_Decrypt() is used | |
463 | to generate a signature. | |
464 | ||
465 | - The output buffer length parameter siglen in C_Sign() | |
466 | is now initialized to the actual size of the output | |
467 | buffer prior to the function call. This fixes the | |
468 | CKR_BUFFER_TOO_SMALL error that could occur when using | |
469 | the OpenSC PKCS#11 module. | |
470 | ||
471 | - Changed the initialization of the PKCS#11 CK_MECHANISM in | |
472 | C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }. | |
473 | ||
474 | - Refactored the RSA public/private key code and transferred it | |
475 | from keys.c to the new pkcs1.c file as a preparatory step | |
476 | towards the release of the SCEP client. | |
477 | ||
478 | ||
479 | strongswan-2.5.0 | |
480 | ---------------- | |
481 | ||
482 | - The loading of a PKCS#11 smartcard library module during | |
483 | runtime does not require OpenSC library functions any more | |
484 | because the corresponding code has been integrated into | |
485 | smartcard.c. Also the RSAREF pkcs11 header files have been | |
486 | included in a newly created pluto/rsaref directory so that | |
487 | no external include path has to be defined any longer. | |
488 | ||
489 | - A long-awaited feature has been implemented at last: | |
490 | The local caching of CRLs fetched via HTTP or LDAP, activated | |
491 | by the parameter cachecrls=yes in the config setup section | |
492 | of ipsec.conf. The dynamically fetched CRLs are stored under | |
493 | a unique file name containing the issuer's subjectKeyID | |
494 | in /etc/ipsec.d/crls. | |
495 | ||
496 | - Applied a one-line patch courtesy of Michael Richardson | |
497 | from the Openswan project which fixes the kernel-oops | |
498 | in KLIPS when an snmp daemon is running on the same box. | |
499 | ||
500 | ||
501 | strongswan-2.4.4 | |
502 | ---------------- | |
503 | ||
504 | - Eliminated null length CRL distribution point strings. | |
505 | ||
506 | - Fixed a trust path evaluation bug introduced with 2.4.3 | |
507 | ||
508 | ||
509 | strongswan-2.4.3 | |
510 | ---------------- | |
511 | ||
512 | - Improved the joint OCSP / CRL revocation policy. | |
513 | OCSP responses have precedence over CRL entries. | |
514 | ||
515 | - Introduced support of CRLv2 reason codes. | |
516 | ||
517 | - Fixed a bug with key-pad equipped readers which caused | |
518 | pluto to prompt for the pin via the console when the first | |
519 | occasion to enter the pin via the key-pad was missed. | |
520 | ||
521 | - When pluto is built with LDAP_V3 enabled, the library | |
522 | liblber required by newer versions of openldap is now | |
523 | included. | |
524 | ||
525 | ||
526 | strongswan-2.4.2 | |
527 | ---------------- | |
528 | ||
529 | - Added the _updown_espmark template which requires all | |
530 | incoming ESP traffic to be marked with a default mark | |
531 | value of 50. | |
532 | ||
533 | - Introduced the pkcs11keepstate parameter in the config setup | |
534 | section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11 | |
535 | session and login states are kept as long as possible during | |
536 | the lifetime of pluto. This means that a PIN entry via a key | |
537 | pad has to be done only once. | |
538 | ||
539 | - Introduced the pkcs11module parameter in the config setup | |
540 | section of ipsec.conf which specifies the PKCS#11 module | |
541 | to be used with smart cards. Example: | |
542 | ||
543 | pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo | |
544 | ||
545 | - Added support of smartcard readers equipped with a PIN pad. | |
546 | ||
547 | - Added patch by Jay Pfeifer which detects when netkey | |
548 | modules have been statically built into the Linux 2.6 kernel. | |
549 | ||
550 | - Added two patches by Herbert Xu. The first uses ip xfrm | |
551 | instead of setkey to flush the IPsec policy database. The | |
552 | second sets the optional flag in inbound IPComp SAs only. | |
553 | ||
554 | - Applied Ulrich Weber's patch which fixes an interoperability | |
555 | problem between native IPsec and KLIPS systems caused by | |
556 | setting the replay window to 32 instead of 0 for ipcomp. | |
557 | ||
558 | ||
559 | strongswan-2.4.1 | |
560 | ---------------- | |
561 | ||
562 | - Fixed a bug which caused an unwanted Mode Config request | |
563 | to be initiated in the case where "right" was used to denote | |
564 | the local side in ipsec.conf and "left" the remote side, | |
565 | contrary to the recommendation that "right" be remote and | |
566 | "left" be"local". | |
567 | ||
568 | ||
569 | strongswan-2.4.0a | |
570 | ----------------- | |
571 | ||
572 | - updated Vendor ID to strongSwan-2.4.0 | |
573 | ||
574 | - updated copyright statement to include David Buechi and | |
575 | Michael Meier | |
576 | ||
577 | ||
578 | strongswan-2.4.0 | |
579 | ---------------- | |
580 | ||
581 | - strongSwan now communicates with attached smartcards and | |
582 | USB crypto tokens via the standardized PKCS #11 interface. | |
583 | By default the OpenSC library from www.opensc.org is used | |
584 | but any other PKCS#11 library could be dynamically linked. | |
585 | strongSwan's PKCS#11 API was implemented by David Buechi | |
586 | and Michael Meier, both graduates of the Zurich University | |
587 | of Applied Sciences in Winterthur, Switzerland. | |
588 | ||
589 | - When a %trap eroute is triggered by an outgoing IP packet | |
590 | then the native IPsec stack of the Linux 2.6 kernel [often/ | |
591 | always?] returns an XFRM_ACQUIRE message with an undefined | |
592 | protocol family field and the connection setup fails. | |
593 | As a workaround IPv4 (AF_INET) is now assumed. | |
594 | ||
595 | - the results of the UML test scenarios are now enhanced | |
596 | with block diagrams of the virtual network topology used | |
597 | in a particular test. | |
598 | ||
599 | ||
600 | strongswan-2.3.2 | |
601 | ---------------- | |
602 | ||
603 | - fixed IV used to decrypt informational messages. | |
604 | This bug was introduced with Mode Config functionality. | |
605 | ||
606 | - fixed NCP Vendor ID. | |
607 | ||
608 | - undid one of Ulrich Weber's maximum udp size patches | |
609 | because it caused a segmentation fault with NAT-ed | |
610 | Delete SA messages. | |
611 | ||
612 | - added UML scenarios wildcards and attr-cert which | |
613 | demonstrate the implementation of IPsec policies based | |
614 | on wildcard parameters contained in Distinguished Names and | |
615 | on X.509 attribute certificates, respectively. | |
616 | ||
617 | ||
618 | strongswan-2.3.1 | |
619 | ---------------- | |
620 | ||
621 | - Added basic Mode Config functionality | |
622 | ||
623 | - Added Mathieu Lafon's patch which upgrades the status of | |
624 | the NAT-Traversal implementation to RFC 3947. | |
625 | ||
626 | - The _startklips script now also loads the xfrm4_tunnel | |
627 | module. | |
628 | ||
629 | - Added Ulrich Weber's netlink replay window size and | |
630 | maximum udp size patches. | |
631 | ||
632 | - UML testing now uses the Linux 2.6.10 UML kernel by default. | |
633 | ||
634 | ||
635 | strongswan-2.3.0 | |
636 | ---------------- | |
637 | ||
638 | - Eric Marchionni and Patrik Rayo, both recent graduates from | |
639 | the Zuercher Hochschule Winterthur in Switzerland, created a | |
640 | User-Mode-Linux test setup for strongSwan. For more details | |
641 | please read the INSTALL and README documents in the testing | |
642 | subdirectory. | |
643 | ||
644 | - Full support of group attributes based on X.509 attribute | |
645 | certificates. Attribute certificates can be generated | |
646 | using the openac facility. For more details see | |
647 | ||
648 | man ipsec_openac. | |
649 | ||
650 | The group attributes can be used in connection definitions | |
651 | in order to give IPsec access to specific user groups. | |
652 | This is done with the new parameter left|rightgroups as in | |
653 | ||
654 | rightgroups="Research, Sales" | |
655 | ||
656 | giving access to users possessing the group attributes | |
657 | Research or Sales, only. | |
658 | ||
659 | - In Quick Mode clients with subnet mask /32 are now | |
660 | coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should | |
661 | fix rekeying problems with the SafeNet/SoftRemote and NCP | |
662 | Secure Entry Clients. | |
663 | ||
664 | - Changed the defaults of the ikelifetime and keylife parameters | |
665 | to 3h and 1h, respectively. The maximum allowable values are | |
666 | now both set to 24 h. | |
667 | ||
668 | - Suppressed notification wars between two IPsec peers that | |
669 | could e.g. be triggered by incorrect ISAKMP encryption. | |
670 | ||
671 | - Public RSA keys can now have identical IDs if either the | |
672 | issuing CA or the serial number is different. The serial | |
673 | number of a certificate is now shown by the command | |
674 | ||
675 | ipsec auto --listpubkeys | |
676 | ||
677 | ||
678 | strongswan-2.2.2 | |
679 | ---------------- | |
680 | ||
681 | - Added Tuomo Soini's sourceip feature which allows a strongSwan | |
682 | roadwarrior to use a fixed Virtual IP (see README section 2.6) | |
683 | and reduces the well-known four tunnel case on VPN gateways to | |
684 | a single tunnel definition (see README section 2.4). | |
685 | ||
686 | - Fixed a bug occuring with NAT-Traversal enabled when the responder | |
687 | suddenly turns initiator and the initiator cannot find a matching | |
688 | connection because of the floated IKE port 4500. | |
689 | ||
690 | - Removed misleading ipsec verify command from barf. | |
691 | ||
692 | - Running under the native IP stack, ipsec --version now shows | |
693 | the Linux kernel version (courtesy to the Openswan project). | |
694 | ||
695 | ||
696 | strongswan-2.2.1 | |
697 | ---------------- | |
698 | ||
699 | - Introduced the ipsec auto --listalgs monitoring command which lists | |
700 | all currently registered IKE and ESP algorithms. | |
701 | ||
702 | - Fixed a bug in the ESP algorithm selection occuring when the strict flag | |
703 | is set and the first proposed transform does not match. | |
704 | ||
705 | - Fixed another deadlock in the use of the lock_certs_and_keys() mutex, | |
706 | occuring when a smartcard is present. | |
707 | ||
708 | - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event. | |
709 | ||
710 | - Fixed the printing of the notification names (null) | |
711 | ||
712 | - Applied another of Herbert Xu's Netlink patches. | |
713 | ||
714 | ||
715 | strongswan-2.2.0 | |
716 | ---------------- | |
717 | ||
718 | - Support of Dead Peer Detection. The connection parameter | |
719 | ||
720 | dpdaction=clear|hold | |
721 | ||
722 | activates DPD for the given connection. | |
723 | ||
724 | - The default Opportunistic Encryption (OE) policy groups are not | |
725 | automatically included anymore. Those wishing to activate OE can include | |
726 | the policy group with the following statement in ipsec.conf: | |
727 | ||
728 | include /etc/ipsec.d/examples/oe.conf | |
729 | ||
730 | The default for [right|left]rsasigkey is now set to %cert. | |
731 | ||
732 | - strongSwan now has a Vendor ID of its own which can be activated | |
733 | using the compile option VENDORID | |
734 | ||
735 | - Applied Herbert Xu's patch which sets the compression algorithm correctly. | |
736 | ||
737 | - Applied Herbert Xu's patch fixing an ESPINUDP problem | |
738 | ||
739 | - Applied Herbert Xu's patch setting source/destination port numbers. | |
740 | ||
741 | - Reapplied one of Herbert Xu's NAT-Traversal patches which got | |
742 | lost during the migration from SuperFreeS/WAN. | |
743 | ||
744 | - Fixed a deadlock in the use of the lock_certs_and_keys() mutex. | |
745 | ||
746 | - Fixed the unsharing of alg parameters when instantiating group | |
747 | connection. | |
748 | ||
749 | ||
750 | strongswan-2.1.5 | |
751 | ---------------- | |
752 | ||
753 | - Thomas Walpuski made me aware of a potential DoS attack via | |
754 | a PKCS#7-wrapped certificate bundle which could overwrite valid CA | |
755 | certificates in Pluto's authority certificate store. This vulnerability | |
756 | was fixed by establishing trust in CA candidate certificates up to a | |
757 | trusted root CA prior to insertion into Pluto's chained list. | |
758 | ||
759 | - replaced the --assign option by the -v option in the auto awk script | |
760 | in order to make it run with mawk under debian/woody. | |
761 | ||
762 | ||
763 | strongswan-2.1.4 | |
764 | ---------------- | |
765 | ||
766 | - Split of the status information between ipsec auto --status (concise) | |
767 | and ipsec auto --statusall (verbose). Both commands can be used with | |
768 | an optional connection selector: | |
769 | ||
770 | ipsec auto --status[all] <connection_name> | |
771 | ||
772 | - Added the description of X.509 related features to the ipsec_auto(8) | |
773 | man page. | |
774 | ||
775 | - Hardened the ASN.1 parser in debug mode, especially the printing | |
776 | of malformed distinguished names. | |
777 | ||
778 | - The size of an RSA public key received in a certificate is now restricted to | |
779 | ||
780 | 512 bits <= modulus length <= 8192 bits. | |
781 | ||
782 | - Fixed the debug mode enumeration. | |
783 | ||
784 | ||
785 | strongswan-2.1.3 | |
786 | ---------------- | |
787 | ||
788 | - Fixed another PKCS#7 vulnerability which could lead to an | |
789 | endless loop while following the X.509 trust chain. | |
790 | ||
791 | ||
792 | strongswan-2.1.2 | |
793 | ---------------- | |
794 | ||
795 | - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski | |
796 | that accepted end certificates having identical issuer and subject | |
797 | distinguished names in a multi-tier X.509 trust chain. | |
798 | ||
799 | ||
800 | strongswan-2.1.1 | |
801 | ---------------- | |
802 | ||
803 | - Removed all remaining references to ipsec_netlink.h in KLIPS. | |
804 | ||
805 | ||
806 | strongswan-2.1.0 | |
807 | ---------------- | |
808 | ||
809 | - The new "ca" section allows to define the following parameters: | |
810 | ||
811 | ca kool | |
812 | cacert=koolCA.pem # cacert of kool CA | |
813 | ocspuri=http://ocsp.kool.net:8001 # ocsp server | |
814 | ldapserver=ldap.kool.net # default ldap server | |
815 | crluri=http://www.kool.net/kool.crl # crl distribution point | |
816 | crluri2="ldap:///O=Kool, C= .." # crl distribution point #2 | |
817 | auto=add # add, ignore | |
818 | ||
819 | The ca definitions can be monitored via the command | |
820 | ||
821 | ipsec auto --listcainfos | |
822 | ||
823 | - Fixed cosmetic corruption of /proc filesystem by integrating | |
824 | D. Hugh Redelmeier's freeswan-2.06 kernel fixes. | |
825 | ||
826 | ||
827 | strongswan-2.0.2 | |
828 | ---------------- | |
829 | ||
830 | - Added support for the 818043 NAT-Traversal update of Microsoft's | |
831 | Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode. | |
832 | ||
833 | - A symbolic link to libcrypto is now added in the kernel sources | |
834 | during kernel compilation | |
835 | ||
836 | - Fixed a couple of 64 bit issues (mostly casts to int). | |
837 | Thanks to Ken Bantoft who checked my sources on a 64 bit platform. | |
838 | ||
839 | - Replaced s[n]printf() statements in the kernel by ipsec_snprintf(). | |
840 | Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro | |
841 | of the FreeS/WAN team who solved this problem with the 2.4.25 kernel. | |
842 | ||
843 | ||
844 | strongswan-2.0.1 | |
845 | ---------------- | |
846 | ||
847 | - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName | |
848 | certificate extension which contains no generalName item) can cause | |
849 | a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has | |
850 | been hardened to make it more robust against malformed ASN.1 objects. | |
851 | ||
852 | - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native | |
853 | Linux 2.6 IPsec stack. | |
854 | ||
855 | ||
856 | strongswan-2.0.0 | |
857 | ---------------- | |
858 | ||
859 | - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12 |