1: strongswan-5.9.2
2: ----------------
3:
4: - Together with a Linux 5.8 kernel supporting the IMA measurement of the GRUB
5: bootloader and the Linux kernel, the strongSwan Attestation IMC allows to do
6: remote attestation of the complete boot phase. A recent TPM 2.0 device with a
7: SHA-256 PCR bank is required, so that both BIOS and IMA file measurements are
8: based on SHA-256 hashes.
9:
10: - Our own TLS library (libtls) that we use for TLS-based EAP methods and PT-TLS
11: gained experimental support for TLS 1.3. Thanks to Méline Sieber (client) and
12: Pascal Knecht (client and server) for their work on this.
13: Because the use of TLS 1.3 with these EAP methods is not yet standardized (two
14: Internet-Drafts are being worked on), the default maximum version is currently
15: set to TLS 1.2, which is now also the default minimum version. However the TNC
16: test scenarios using PT-TLS transport already use TLS 1.3.
17:
18: - Other improvements for libtls also affect older TLS versions. For instance, we
19: added support for ECDH with Curve25519/448 (DH groups may also be configured
20: now), for EdDSA keys and certificates and for RSA-PSS signatures. Support for
21: old and weak cipher suites has been removed (e.g. with 3DES and MD5) as well
22: as signature schemes with SHA-1.
23:
24: - The listener_t::ike_update event is now also called for MOBIKE updates. Its
25: signature has changed so we only have to call it once if both addresses/ports
26: have changed (e.g. for an address family switch). The event is now also
27: exposed via vici.
28:
29: - The farp plugin has been ported to macOS and FreeBSD. Thanks to Dan James for
30: working on this.
31:
32: - To fix DNS server installation with systemd-resolved, charon-nm now creates a
33: dummy TUN device again (was removed with 5.5.1).
34:
35: - The botan plugin can use rng_t implementations provided by other plugins when
36: generating keys etc. if the Botan library supports it.
37:
38: - charon-tkm now supports multiple CAs and is configured via vici/swanctl.
39:
40: - Simple glob patterns (e.g. include conf.d/*.conf) now also work on Windows.
41: Handling of forward slashes in paths on Windows has also been improved.
42:
43: - The abbreviations for the 'surname' and 'serial number' RDNs in ASN.1 DNs have
44: been changed to align with RFC 4519: The abbreviation for 'surname' is now
45: "SN" (was "S" before), which was previously used for 'serial number' that can
46: now be specified as "serialNumber" only.
47:
48: - An issue with Windows clients requesting previous IPv6 but not IPv4 virtual
49: IP addresses has been fixed.
50:
51: - ike_sa_manager_t: Checking out IKE_SAs by config is now atomic (e.g. when
52: acquires for different children of the same connection arrive concurrently).
53: The checkout_new() method has been renamed to create_new(). A new
54: checkout_new() method allows registering a new IKE_SA with the manager before
55: checking it in, so jobs can be queued without losing them as they can block
56: on checking out the new SA.
57:
58:
59: strongswan-5.9.1
60: ----------------
61:
62: - Remote attestation via TNC supports the SHA-256 based TPM 2.0 BIOS/EFI
63: measurements introduced with the Linux 5.4 kernel.
64:
65: - Nonces in OCSP responses are not enforced anymore and only validated if a
66: nonce is actually contained.
67:
68: - Fixed an issue when only some fragments of a retransmitted IKEv2 message were
69: received, which prevented processing a following fragmented message.
70:
71: - All queued vici messages are now sent to subscribed clients during shutdown,
72: which includes ike/child-updown events triggered when all SAs are deleted.
73:
74: - CHILD_SA IP addresses are updated before installation to allow MOBIKE updates
75: while retransmitting a CREATE_CHILD_SA request.
76:
77: - When looking for a route to the peer, the kernel-netlink plugin ignores the
78: current source address if it's deprecated.
79:
80: - The file and syslog loggers support logging the log level of each message
81: after the subsystem (e.g. [IKE2]).
82:
83: - charon-nm is now properly terminated during system shutdown.
84:
85: - Improved support for EdDSA keys in vici/swanctl, in particular, encrypted
86: keys are now supported.
87:
88: - A new global strongswan.conf option allows sending the Cisco FlexVPN vendor ID
89: to prevent Cisco devices from narrowing a 0.0.0.0/0 traffic selector.
90:
91: - The openssl plugin accepts CRLs issued by non-CA certificates if they contain
92: the cRLSign keyUsage flag (the x509 plugin already does this since 4.5.1).
93:
94: - Attributes in PKCS#7 containers, as used in SCEP, are now properly
95: DER-encoded, i.e. sorted.
96:
97: - The load-tester plugin now supports virtual IPv6 addresses and IPv6 source
98: address pools.
99:
100:
101: strongswan-5.9.0
102: ----------------
103:
104: - We prefer AEAD algorithms for ESP and therefore put AES-GCM in a default AEAD
105: proposal in front of the previous default proposal.
106:
107: - The NM backend now clears cached credentials when disconnecting, has DPD and
108: and close action set to restart, and supports custom remote TS via 'remote-ts'
109: option (no GUI support).
110:
111: - The pkcs11 plugin falls back to software hashing for PKCS#1v1.5 RSA signatures
112: if mechanisms with hashing (e.g. CKM_SHA256_RSA_PKCS) are not supported.
113:
114: - The owner/group of log files is now set so the daemon can reopen them if the
115: config is reloaded and it doesn't run as root.
116:
117: - The wolfssl plugin (with wolfSSL 4.4.0+) supports x448 DH and Ed448 keys.
118:
119: - The vici plugin stores all CA certificates in one location, which avoids
120: issues with unloading authority sections or clearing all credentials.
121:
122: - When unloading a vici connection with start_action=start, any related IKE_SAs
123: without children are now terminated (including those in CONNECTING state).
124:
125: - The hashtable implementation has been changed so it maintains insertion order.
126: This was mainly done so the vici plugin can store its connections in a
127: hashtable, which makes managing high numbers of connections faster.
128:
129: - The default maximum size for vici messages (512 KiB) can now be changed via
130: VICI_MESSAGE_SIZE_MAX compile option.
131:
132: - The charon.check_current_path option allows forcing a DPD exchange to check if
133: the current path still works whenever interface/address-changes are detected.
134:
135: - It's possible to use clocks other than CLOCK_MONOTONIC (e.g. CLOCK_BOOTTIME)
136: via TIME_CLOCK_ID compile option if clock_gettime() is available and
137: pthread_condattr_setclock() supports that clock.
138:
139: - Test cases and functions can now be filtered when running the unit tests.
140:
141:
142: strongswan-5.8.4
143: ----------------
144:
145: - In IKEv1 Quick Mode make sure that a proposal exists before determining
146: lifetimes (fixes crash due to null pointer exception).
147:
148: - OpenSSL currently doesn't support squeezing bytes out of a SHAKE128/256
149: XOF (eXtended Output Function) multiple times. Unfortunately,
150: EVP_DigestFinalXOF() completely resets the context and later calls not
151: simply fail, they cause a null-pointer dereference in libcrypto. This
152: fixes the crash at the cost of repeating initializing the whole state
153: and allocating too much data for subsequent calls.
154:
155:
156: strongswan-5.8.3
157: ----------------
158:
159: - Updates for the NM backend (and plugin), among others: EAP-TLS authentication,
160: configurable local and remote IKE identities, custom server port, redirection
161: and reauthentication support.
162:
163: - Previously used reqids are now reallocated to workaround an issue on FreeBSD
164: where the daemon can't use reqids > 16383.
165:
166: - On Linux, throw type routes are installed for passthrough policies. They act
167: as fallbacks on routes in other tables and require less information, so they
168: can be installed earlier and are not affected by updates.
169:
170: - For IKEv1, the lifetimes of the selected transform are returned to the
171: initiator, which is an issue with peers that propose different lifetimes in
172: different transforms. We also return the correct transform and proposal IDs.
173:
174: - IKE_SAs are not re-established anymore if a deletion has been queued.
175:
176: - Added support for Ed448 keys and certificates via openssl plugin and pki tool.
177: The openssl plugin also supports SHA-3 and SHAKE128/256.
178:
179: - The use of algorithm IDs from the private use ranges can now be enabled
180: globally, to use them even if no strongSwan vendor ID was exchanged.
181:
182:
183: strongswan-5.8.2
184: ----------------
185:
186: - Identity-based CA constraints are supported via vici/swanctl.conf. They
187: enforce that the remote's certificate chain contains a CA certificate with a
188: specific identity. While similar to the existing CA constraints, they don't
189: require that the CA certificate is locally installed such as intermediate CA
190: certificates received from peers. Compared to wildcard identity matching (e.g.
191: "..., OU=Research, CN=*") this requires less trust in the intermediate CAs (to
192: only issue certificates with legitimate subject DNs) as long as path length
193: basic constraints prevent them from issuing further intermediate CAs.
194:
195: - Intermediate CA certificates may now be sent in hash-and-URL encoding by
196: configuring a base URL for the parent CA.
197:
198: - Implemented NIST SP-800-90A Deterministic Random Bit Generator (DRBG)
199: based on AES-CTR and SHA2-HMAC modes. Currently used by gmp and ntru plugins.
200:
201: - Random nonces sent in an OCSP requests are now expected in the corresponding
202: OCSP responses.
203:
204: - The kernel-netlink plugin ignores deprecated IPv6 addresses for MOBIKE.
205: Whether temporary or permanent IPv6 addresses are included depends on the
206: charon.prefer_temporary_addrs setting.
207:
208: - Extended Sequence Numbers (ESN) are configured via PF_KEY if supported by the
209: kernel.
210:
211: - Unique section names are used for CHILD_SAs in vici child-updown events and
212: more information (e.g. statistics) are included for individually deleted
213: CHILD_SAs (in particular for IKEv1).
214:
215: - So fallbacks to other plugins work properly, creating HMACs via openssl plugin
216: now fails instantly if the underlying hash algorithm isn't supported (e.g.
217: MD5 in FIPS-mode).
218:
219: - Exponents of RSA keys read from TPM 2.0 via SAPI are now correctly converted.
220:
221: - Routing table IDs > 255 are supported for custom routes on Linux.
222:
223: - The D-Bus config file for charon-nm is now installed in
224: $(datadir)/dbus-1/system.d instead of $(sysconfdir)/dbus-1/system.d.
225:
226: - INVALID_MAJOR_VERSION notifies are now correctly sent in messages of the same
227: exchange type and using the same message ID as the request.
228:
229: - IKEv2 SAs are immediately destroyed when sending or receiving INVALID_SYNTAX
230: notifies in authenticated messages.
231:
232:
233: strongswan-5.8.1
234: ----------------
235:
236: - RDNs in Distinguished Names can now optionally be matched less strict. The
237: global option charon.rdn_matching takes two alternative values that cause the
238: matching algorithm to either ignore the order of matched RDNs or additionally
239: accept DNs that contain more RDNs than configured (unmatched RDNs are treated
240: like wildcard matches).
241:
242: - The updown plugin now passes the same interface to the script that is also
243: used for the automatically installed routes, i.e. the interface over which the
244: peer is reached instead of the interface on which the local address is found.
245:
246: - TPM 2.0 contexts are now protected by a mutex to prevent issues if multiple
247: IKE_SAs use the same private key concurrently.
248:
249:
250: strongswan-5.8.0
251: ----------------
252:
253: - The systemd service units have been renamed. The modern unit, which was called
254: strongswan-swanctl, is now called strongswan (the previous name is configured
255: as alias). The legacy unit is now called strongswan-starter.
256:
257: - Support for XFRM interfaces (available since Linux 4.19) has been added.
258: Configuration is possible via swanctl.conf. Interfaces may be created
259: dynamically via updown/vici scripts, or statically before or after
260: establishing the SAs. Routes must be added manually as needed (the daemon will
261: not install any routes for outbound policies with an interface ID).
262:
263: - Initiation of childless IKE_SAs is supported (RFC 6023). If enabled and
264: supported by the responder, no CHILD_SA is established during IKE_AUTH. This
265: allows using a separate DH exchange even for the first CHILD_SA, which is
266: otherwise created with keys derived from the IKE_SA's key material.
267:
268: - The NetworkManager backend and plugin support IPv6.
269:
270: - The new wolfssl plugin is a wrapper around the wolfSSL crypto library. Thanks
271: to Sean Parkinson of wolfSSL Inc. for the initial patch.
272:
273: - IKE SPIs may optionally be labeled via the charon.spi_mask|label options. This
274: feature was extracted from charon-tkm, however, now applies the mask/label in
275: network order.
276:
277: - The openssl plugin supports ChaCha20-Poly1305 when built with OpenSSL 1.1.0.
278:
279: - The PB-TNC finite state machine according to section 3.2 of RFC 5793 was not
280: correctly implemented when sending either a CRETRY or SRETRY batch. These
281: batches can only be sent in the "Decided" state and a CRETRY batch can
282: immediately carry all messages usually transported by a CDATA batch. It is
283: currently not possible to send a SRETRY batch since full-duplex mode for
284: PT-TLS transport is not supported.
285:
286: - Instead of marking virtual IPv6 addresses as deprecated, the kernel-netlink
287: plugin uses address labels to avoid their use for non-VPN traffic.
288:
289: - The agent plugin creates sockets to the ssh/gpg-agent dynamically and does not
290: keep them open, which otherwise can prevent the agent from getting terminated.
291:
292: - To avoid broadcast loops the forecast plugin now only reinjects packets that
293: are marked or received from the configured interface.
294:
295: - UTF-8 encoded passwords are supported via EAP-MSCHAPv2, which internally uses
296: an UTF-16LE encoding to calculate the NT hash.
297:
298: - Adds the build-certs script to generate the keys and certificates used for
299: regression tests dynamically. They are built with the pki version installed
300: in the KVM root image so it's not necessary to have an up-to-date version with
301: all required plugins installed on the host system.
302:
303:
304: strongswan-5.7.2
305: ----------------
306:
307: - Private key implementations may optionally provide a list of supported
308: signature schemes, which is used by the tpm plugin because for each key on a
309: TPM 2.0 the hash algorithm and for RSA also the padding scheme is predefined.
310:
311: - For RSA with PSS padding, the TPM 2.0 specification mandates the maximum salt
312: length (as defined by the length of the key and hash). However, if the TPM is
313: FIPS-168-4 compliant, the salt length equals the hash length. This is assumed
314: for FIPS-140-2 compliant TPMs, but if that's not the case, it might be
315: necessary to manually enable charon.plugins.tpm.fips_186_4 if the TPM doesn't
316: use the maximum salt length.
317:
318: - swanctl now accesses directories for credentials relative to swanctl.conf, in
319: particular, when it's loaded from a custom location via --file argument. The
320: base directory that's used if --file is not given is configurable at runtime
321: via SWANCTL_DIR environment variable.
322:
323: - With RADIUS Accounting enabled, the eap-radius plugin adds the session ID to
324: Access-Request messages, simplifying associating database entries for IP
325: leases and accounting with sessions.
326:
327: - IPs assigned by RADIUS servers are included in Accounting-Stop even if clients
328: don't claim them, allowing releasing them early on connection errors.
329:
330: - Selectors installed on transport mode SAs by the kernel-netlink plugin are
331: updated on IP address changes (e.g. via MOBIKE).
332:
333: - Added support for RSA signatures with SHA-256 and SHA-512 to the agent plugin.
334: For older versions of ssh/gpg-agent that only support SHA-1, IKEv2 signature
335: authentication has to be disabled via charon.signature_authentication.
336:
337: - The sshkey and agent plugins support Ed25519/Ed448 SSH keys and signatures.
338:
339: - The openssl plugin supports X25519/X448 Diffie-Hellman and Ed25519/Ed448 keys
340: and signatures when built against OpenSSL 1.1.1.
341:
342: - Ed25519, ChaCha20/Poly1305, SHA-3 and AES-CCM were added to the botan plugin.
343:
344: - The mysql plugin now properly handles database connections with transactions
345: under heavy load.
346:
347: - IP addresses in HA pools are now distributed evenly among all segments.
348:
349: - On newer FreeBSD kernels, the kernel-pfkey plugin reads the reqid directly
350: from SADB_ACQUIRE messages, i.e. not requiring previous policy installation by
351: the plugin, e.g. for compatibility with if_ipsec(4) VTIs.
352:
353:
354: strongswan-5.7.1
355: ----------------
356:
357: - Fixes a vulnerability in the gmp plugin triggered by crafted certificates with
358: RSA keys with very small moduli. When verifying signatures with such keys,
359: the code patched with the fix for CVE-2018-16151/2 caused an integer underflow
360: and subsequent heap buffer overflow that results in a crash of the daemon.
361: The vulnerability has been registered as CVE-2018-17540.
362:
363:
364: strongswan-5.7.0
365: ----------------
366:
367: - Fixes a potential authorization bypass vulnerability in the gmp plugin that
368: was caused by a too lenient verification of PKCS#1 v1.5 signatures. Several
369: flaws could be exploited by a Bleichenbacher-style attack to forge signatures
370: for low-exponent keys (i.e. with e=3). CVE-2018-16151 has been assigned to
371: the problem of accepting random bytes after the OID of the hash function in
372: such signatures, and CVE-2018-16152 has been assigned to the issue of not
373: verifying that the parameters in the ASN.1 algorithmIdentifier structure is
374: empty. Other flaws that don't lead to a vulnerability directly (e.g. not
375: checking for at least 8 bytes of padding) have no separate CVE assigned.
376:
377: - Dots are not allowed anymore in section names in swanctl.conf and
378: strongswan.conf. This mainly affects the configuration of file loggers. If the
379: path for such a log file contains dots it now has to be configured in the new
380: `path` setting within the arbitrarily renamed subsection in the `filelog`
381: section.
382:
383: - Sections in swanctl.conf and strongswan.conf may now reference other sections.
384: All settings and subsections from such a section are inherited. This allows
385: to simplify configs as redundant information has only to be specified once
386: and may then be included in other sections (refer to the example in the man
387: page for strongswan.conf).
388:
389: - The originally selected IKE config (based on the IPs and IKE version) can now
390: change if no matching algorithm proposal is found. This way the order
391: of the configs doesn't matter that much anymore and it's easily possible to
392: specify separate configs for clients that require weak algorithms (instead
393: of having to also add them in other configs that might be selected).
394:
395: - Support for Postquantum Preshared Keys for IKEv2 (draft-ietf-ipsecme-qr-ikev2)
396: has been added.
397:
398: - The new botan plugin is a wrapper around the Botan C++ crypto library. It
399: requires a fairly recent build from Botan's master branch (or the upcoming
400: 2.8.0 release). Thanks to René Korthaus and his team from Rohde & Schwarz
401: Cybersecurity for the initial patch.
402:
403: - The pki tool accepts a xmppAddr otherName as a subjectAlternativeName using
404: the syntax --san xmppaddr:<jid>.
405:
406: - Implementation of RFC 8412 "Software Inventory Message and Attributes (SWIMA)
407: for PA-TNC". SWIMA subscription option sets CLOSE_WRITE trigger on apt
408: history.log file resulting in a ClientRetry PB-TNC batch to initialize
409: a new measurement cycle.
410:
411: - Added support for fuzzing the PA-TNC (RFC 5792) and PB-TNC (RFC 5793) NEA
412: protocols on Google's OSS-Fuzz infrastructure.
413:
414: - Support for version 2 of Intel's TPM2-TSS TGC Software Stack. The presence of
415: the in-kernel /dev/tpmrm0 resource manager is automatically detected.
416:
417: - Marks the in- and/or outbound SA should apply to packets after processing may
418: be configured in swanctl.conf on Linux. For outbound SAs this requires at
419: least a 4.14 kernel. Setting a mask and configuring a mark/mask for inbound
420: SAs will be added with the upcoming 4.19 kernel.
421:
422: - New options in swanctl.conf allow configuring how/whether DF, ECN and DS
423: fields in the IP headers are copied during IPsec processing. Controlling this
424: is currently only possible on Linux.
425:
426: - To avoid conflicts, the dhcp plugin now only uses the DHCP server port if
427: explicitly configured.
428:
429:
430: strongswan-5.6.3
431: ----------------
432:
433: - Fixed a DoS vulnerability in the IKEv2 key derivation if the openssl plugin is
434: used in FIPS mode and HMAC-MD5 is negotiated as PRF.
435: This vulnerability has been registered as CVE-2018-10811.
436:
437: - Fixed a vulnerability in the stroke plugin, which did not check the received
438: length before reading a message from the socket. Unless a group is configured,
439: root privileges are required to access that socket, so in the default
440: configuration this shouldn't be an issue.
441: This vulnerability has been registered as CVE-2018-5388.
442:
443: ⁻ CRLs that are not yet valid are now ignored to avoid problems in scenarios
444: where expired certificates are removed from CRLs and the clock on the host
445: doing the revocation check is trailing behind that of the host issuing CRLs.
446:
447: - The issuer of fetched CRLs is now compared to the issuer of the checked
448: certificate.
449:
450: - CRL validation results other than revocation (e.g. a skipped check because
451: the CRL couldn't be fetched) are now stored also for intermediate CA
452: certificates and not only for end-entity certificates, so a strict CRL policy
453: can be enforced in such cases.
454:
455: - In compliance with RFC 4945, section 5.1.3.2, certificates used for IKE must
456: now either not contain a keyUsage extension (like the ones generated by pki)
457: or have at least one of the digitalSignature or nonRepudiation bits set.
458:
459: - New options for vici/swanctl allow forcing the local termination of an IKE_SA.
460: This might be useful in situations where it's known the other end is not
461: reachable anymore, or that it already removed the IKE_SA, so retransmitting a
462: DELETE and waiting for a response would be pointless. Waiting only a certain
463: amount of time for a response before destroying the IKE_SA is also possible
464: by additionally specifying a timeout.
465:
466: - When removing routes, the kernel-netlink plugin now checks if it tracks other
467: routes for the same destination and replaces the installed route instead of
468: just removing it. Same during installation, where existing routes previously
469: weren't replaced. This should allow using traps with virtual IPs on Linux.
470:
471: - The dhcp plugin only sends the client identifier option if identity_lease is
472: enabled. It can also send identities of up to 255 bytes length, instead of
473: the previous 64 bytes. If a server address is configured, DHCP requests are
474: now sent from port 67 instead of 68 to avoid ICMP port unreachables.
475:
476: - Roam events are now completely ignored for IKEv1 SAs.
477:
478: - ChaCha20/Poly1305 is now correctly proposed without key length. For
479: compatibility with older releases the chacha20poly1305compat keyword may be
480: included in proposals to also propose the algorithm with a key length.
481:
482: - Configuration of hardware offload of IPsec SAs is now more flexible and allows
483: a new mode, which automatically uses it if the kernel and device support it.
484:
485: - SHA-2 based PRFs are supported in PKCS#8 files as generated by OpenSSL 1.1.
486:
487: - The pki --verify tool may load CA certificates and CRLs from directories.
488:
489: - Fixed an issue with DNS servers passed to NetworkManager in charon-nm.
490:
491:
492: strongswan-5.6.2
493: ----------------
494:
495: - Fixed a DoS vulnerability in the parser for PKCS#1 RSASSA-PSS signatures that
496: was caused by insufficient input validation. One of the configurable
497: parameters in algorithm identifier structures for RSASSA-PSS signatures is the
498: mask generation function (MGF). Only MGF1 is currently specified for this
499: purpose. However, this in turn takes itself a parameter that specifies the
500: underlying hash function. strongSwan's parser did not correctly handle the
501: case of this parameter being absent, causing an undefined data read.
502: This vulnerability has been registered as CVE-2018-6459.
503:
504: - The previously negotiated DH group is reused when rekeying an SA, instead of
505: using the first group in the configured proposals, which avoids an additional
506: exchange if the peer selected a different group via INVALID_KE_PAYLOAD when
507: the SA was created initially.
508: The selected DH group is also moved to the front of all sent proposals that
509: contain it and all proposals that don't are moved to the back in order to
510: convey the preference for this group to the peer.
511:
512: - Handling of MOBIKE task queuing has been improved. In particular, the response
513: to an address update is not ignored anymore if only an address list update or
514: DPD is queued.
515:
516: - The fallback drop policies installed to avoid traffic leaks when replacing
517: addresses in installed policies are now replaced by temporary drop policies,
518: which also prevent acquires because we currently delete and reinstall IPsec
519: SAs to update their addresses.
520:
521: - Access X.509 certificates held in non-volatile storage of a TPM 2.0
522: referenced via the NV index.
523:
524: - Adding the --keyid parameter to pki --print allows to print private keys
525: or certificates stored in a smartcard or a TPM 2.0.
526:
527: - Fixed proposal selection if a peer incorrectly sends DH groups in the ESP
528: proposals during IKE_AUTH and also if a DH group is configured in the local
529: ESP proposal and charon.prefer_configured_proposals is disabled.
530:
531: - MSKs received via RADIUS are now padded to 64 bytes to avoid compatibility
532: issues with EAP-MSCHAPv2 and PRFs that have a block size < 64 bytes (e.g.
533: AES-XCBC-PRF-128).
534:
535: - The tpm_extendpcr command line tool extends a digest into a TPM PCR.
536:
537: - Ported the NetworkManager backend from the deprecated libnm-glib to libnm.
538:
539: - The save-keys debugging/development plugin saves IKE and/or ESP keys to files
540: compatible with Wireshark.
541:
542:
543: strongswan-5.6.1
544: ----------------
545:
546: - In compliance with RFCs 8221 and 8247 several algorithms were removed from the
547: default ESP/AH and IKEv2 proposals, respectively (3DES, Blowfish and MD5 from
548: ESP/AH, MD5 and MODP-1024 from IKEv2). These algorithms may still be used in
549: custom proposals.
550:
551: - Added support for RSASSA-PSS signatures. For backwards compatibility they are
552: not used automatically by default, enable charon.rsa_pss to change that. To
553: explicitly use or require such signatures with IKEv2 signature authentication
554: (RFC 7427), regardless of whether that option is enabled, use ike:rsa/pss...
555: authentication constraints.
556:
557: - The pki tool can optionally sign certificates/CRLs with RSASSA-PSS via the
558: `--rsa-padding pss` option.
559:
560: - The sec-updater tool checks for security updates in dpkg-based repositories
561: (e.g. Debian/Ubuntu) and sets the security flags in the IMV policy database
562: accordingly. Additionally for each new package version a SWID tag for the
563: given OS and HW architecture is created and stored in the database.
564: Using the sec-updater.sh script template the lookup can be automated
565: (e.g. via an hourly cron job).
566:
567: - The introduction of file versions in the IMV database scheme broke file
568: reference hash measurements. This has been fixed by creating generic product
569: versions having an empty package name.
570:
571: - A new timeout option for the systime-fix plugin stops periodic system time
572: checks after a while and enforces a certificate verification, closing or
573: reauthenticating all SAs with invalid certificates.
574:
575: - The IKE event counters, previously only available via ipsec listcounters, may
576: now be queried/reset via vici and the new swanctl --counters command. They are
577: provided by the new optional counters plugin.
578:
579: - Class attributes received in RADIUS Access-Accept messages may optionally be
580: added to RADIUS accounting messages.
581:
582: - Inbound marks may optionally be installed on the SA again (was removed with
583: 5.5.2) by enabling the mark_in_sa option in swanctl.conf.
584:
585:
586: strongswan-5.6.0
587: ----------------
588:
589: - Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
590: input validation when verifying RSA signatures, which requires decryption
591: with the operation m^e mod n, where m is the signature, and e and n are the
592: exponent and modulus of the public key. The value m is an integer between
593: 0 and n-1, however, the gmp plugin did not verify this. So if m equals n the
594: calculation results in 0, in which case mpz_export() returns NULL. This
595: result wasn't handled properly causing a null-pointer dereference.
596: This vulnerability has been registered as CVE-2017-11185.
597:
598: - New SWIMA IMC/IMV pair implements the "draft-ietf-sacm-nea-swima-patnc"
599: Internet Draft and has been demonstrated at the IETF 99 Prague Hackathon.
600:
601: - The IMV database template has been adapted to achieve full compliance
602: with the ISO 19770-2:2015 SWID tag standard.
603:
604: - The sw-collector tool extracts software events from apt history logs
605: and stores them in an SQLite database to be used by the SWIMA IMC.
606: The tool can also generate SWID tags both for installed and removed
607: package versions.
608:
609: - The pt-tls-client can attach and use TPM 2.0 protected private keys
610: via the --keyid parameter.
611:
612: - libtpmtss supports Intel's TSS2 Architecture Broker and Resource
613: Manager interface (tcti-tabrmd).
614:
615: - The new eap-aka-3gpp plugin implements the 3GPP MILENAGE algorithms
616: in software. K (optionally concatenated with OPc) may be configured as
617: binary EAP secret.
618:
619: - CHILD_SA rekeying was fixed in charon-tkm and was slightly changed: The
620: switch to the new outbound IPsec SA now happens via SPI on the outbound
621: policy on Linux, and in case of lost rekey collisions no outbound SA/policy
622: is temporarily installed for the redundant CHILD_SA.
623:
624: - The new %unique-dir value for mark* settings allocates separate unique marks
625: for each CHILD_SA direction (in/out).
626:
627:
628: strongswan-5.5.3
629: ----------------
630:
631: - Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient
632: input validation when verifying RSA signatures. More specifically,
633: mpz_powm_sec() has two requirements regarding the passed exponent and modulus
634: that the plugin did not enforce, if these are not met the calculation will
635: result in a floating point exception that crashes the whole process.
636: This vulnerability has been registered as CVE-2017-9022.
637:
638: - Fixed a DoS vulnerability in the x509 plugin that was caused because the ASN.1
639: parser didn't handle ASN.1 CHOICE types properly, which could result in an
640: infinite loop when parsing X.509 extensions that use such types.
641: This vulnerability has been registered as CVE-2017-9023.
642:
643: - The behavior during IKEv2 CHILD_SA rekeying has been changed in order to avoid
644: traffic loss. The responder now only installs the new inbound SA and delays
645: installing the outbound SA until it receives the DELETE for the replaced
646: CHILD_SA. Similarly, the inbound SA of the replaced CHILD_SA is not removed
647: for a configurable amount of seconds (charon.delete_rekeyed_delay) after the
648: DELETE has been processed to reduce the chance of dropping delayed packets.
649:
650: - The code base has been ported to Apple's ARM64 iOS platform, whose calling
651: conventions for variadic and regular functions are different. This means
652: assigning non-variadic functions to variadic function pointers does not work.
653: To avoid this issue the enumerator_t interface has been changed and the
654: signatures of the callback functions for enumerator_create_filter(), and the
655: invoke_function() and find_first() methods on linked_list_t have been changed.
656: The return type of find_first() also changed from status_t to bool.
657:
658: - Added support for fuzzing the certificate parser provided by the default
659: plugins (x509, pem, gmp etc.) on Google's OSS-Fuzz infrastructure. Several
660: issues found while fuzzing these plugins were fixed.
661:
662: - Two new options have been added to charon's retransmission settings:
663: retransmit_limit and retransmit_jitter. The former adds an upper limit to the
664: calculated retransmission timeout, the latter randomly reduces it.
665:
666: - A bug in swanctl's --load-creds command was fixed that caused unencrypted
667: private keys to get unloaded if the command was called multiple times. The
668: load-key VICI command now returns the key ID of the loaded key on success.
669:
670: - The credential manager now enumerates local credential sets before global
671: ones. This means certificates supplied by the peer will now be preferred over
672: certificates with the same identity that may be locally stored (e.g. in the
673: certificate cache).
674:
675: - Added support for hardware offload of IPsec SAs as introduced by Linux 4.11
676: for hardware that supports this.
677:
678: - When building the libraries monolithically and statically the plugin
679: constructors are now hard-coded in each library so the plugin code is not
680: removed by the linker because it thinks none of their symbols are ever
681: referenced.
682:
683: - The pki tool loads the curve25519 plugin by default.
684:
685:
686: strongswan-5.5.2
687: ----------------
688:
689: - Support of Diffie-Hellman group 31 using Curve25519 for IKE as defined
690: by RFC 8031.
691:
692: - Support of Ed25519 digital signature algorithm for IKEv2 as defined by
693: draft-ietf-ipsecme-eddsa. Ed25519-based public key pairs, X.509 certificates
694: and CRLs can be generated and printed by the pki tool.
695:
696: - The new "tpm" libtpmtss plugin allows to use persistent private RSA and ECDSA
697: keys bound to a TPM 2.0 for both IKE and TLS authentication. Using the
698: TPM 2.0 object handle as keyid parameter, the pki --pub tool can extract
699: the public key from the TPM thereby replacing the aikpub2 tool. In a similar
700: fashion pki --req can generate a PKCS#10 certificate request signed with
701: the TPM private key.
702:
703: - The pki tool gained support for generating certificates with the RFC 3779
704: addrblock extension. The charon addrblock plugin now dynamically narrows
705: traffic selectors based on the certificate addrblocks instead of rejecting
706: non-matching selectors completely. This allows generic connections, where
707: the allowed selectors are defined by the used certificates only.
708:
709: - In-place update of cached base and delta CRLs does not leave dozens
710: of stale copies in cache memory.
711:
712: - Several new features for the VICI interface and the swanctl utility: Querying
713: specific pools, enumerating and unloading keys and shared secrets, loading
714: keys and certificates from PKCS#11 tokens, the ability to initiate, install
715: and uninstall connections and policies by their exact name (if multiple child
716: sections in different connections share the same name), a command to initiate
717: the rekeying of IKE and IPsec SAs, support for settings previously only
718: supported by the old config files (plain pubkeys, dscp, certificate policies,
719: IPv6 Transport Proxy Mode, NT Hash secrets, mediation extension).
720:
721: Important: Due to issues with VICI bindings that map sub-sections to
722: dictionaries the CHILD_SA sections returned via list-sas now have a unique
723: name, the original name of a CHILD_SA is returned in the "name" key of its
724: section.
725:
726:
727: strongswan-5.5.1
728: ----------------
729:
730: - The newhope plugin implements the post-quantum NewHope key exchange algorithm
731: proposed in their 2015 paper by Erdem Alkim, Léo Ducas, Thomas Pöppelmann and
732: Peter Schwabe.
733:
734: - The libstrongswan crypto factory now offers the registration of Extended
735: Output Functions (XOFs). Currently supported XOFs are SHAKE128 and SHAKE256
736: implemented by the sha3 plugin, ChaCHa20 implemented by the chapoly plugin
737: and the more traditional MGF1 Mask Generation Functions based on the SHA-1,
738: SHA-256 and SHA-512 hash algorithms implemented by the new mgf1 plugin.
739:
740: - The pki tool, with help of the pkcs1 or openssl plugins, can parse private
741: keys in any of the supported formats without having to know the exact type.
742: So instead of having to specify rsa or ecdsa explicitly the keyword priv may
743: be used to indicate a private key of any type. Similarly, swanctl can load
744: any type of private key from the swanctl/private directory.
745:
746: - The pki tool can handle RSASSA-PKCS1v1.5-with-SHA-3 signatures using the
747: sha3 and gmp plugins.
748:
749: - The VICI flush-certs command flushes certificates from the volatile
750: certificate cache. Optionally the type of the certificates to be
751: flushed (e.g. type = x509_crl) can be specified.
752:
753: - Setting cache_crls = yes in strongswan.conf the vici plugin saves regular,
754: base and delta CRLs to disk.
755:
756: - IKE fragmentation is now enabled by default with the default fragment size
757: set to 1280 bytes for both IP address families.
758:
759: - libtpmtss: In the TSS2 API the function TeardownSocketTcti() was replaced by
760: tss2_tcti_finalize().
761:
762:
763: strongswan-5.5.0
764: ----------------
765:
766: - The new libtpmtss library offers support for both TPM 1.2 and TPM 2.0
767: Trusted Platform Modules. This allows the Attestation IMC/IMV pair to
768: do TPM 2.0 based attestation.
769:
770: - The behavior during IKEv2 exchange collisions has been improved/fixed in
771: several corner cases and support for TEMPORARY_FAILURE and CHILD_SA_NOT_FOUND
772: notifies, as defined by RFC 7296, has been added.
773:
774: - IPsec policy priorities can be set manually (e.g. for high-priority drop
775: policies) and outbound policies may be restricted to a network interface.
776:
777: - The scheme for the automatically calculated default priorities has been
778: changed and now also considers port masks, which were added with 5.4.0.
779:
780: - FWD policies are now installed in both directions in regards to the traffic
781: selectors. Because such "outbound" FWD policies could conflict with "inbound"
782: FWD policies of other SAs they are installed with a lower priority and don't
783: have a reqid set, which allows kernel plugins to distinguish between the two
784: and prefer those with a reqid.
785:
786: - For outbound IPsec SAs no replay window is configured anymore.
787:
788: - Enhanced the functionality of the swanctl --list-conns command by listing
789: IKE_SA and CHILD_SA reauthentication and rekeying settings, and EAP/XAuth
790: identities and EAP types.
791:
792: - DNS servers installed by the resolve plugin are now refcounted, which should
793: fix its use with make-before-break reauthentication. Any output written to
794: stderr/stdout by resolvconf is now logged.
795:
796: - The methods in the kernel interfaces have been changed to take structs instead
797: of long lists of arguments. Similarly the constructors for peer_cfg_t and
798: child_cfg_t now take structs.
799:
800:
801: strongswan-5.4.0
802: ----------------
803:
804: - Support for IKEv2 redirection (RFC 5685) has been added. Plugins may
805: implement the redirect_provider_t interface to decide if and when to redirect
806: connecting clients. It is also possible to redirect established IKE_SAs based
807: on different selectors via VICI/swanctl. Unless disabled in strongswan.conf
808: the charon daemon will follow redirect requests received from servers.
809:
810: - The ike: prefix enables the explicit configuration of signature scheme
811: constraints against IKEv2 authentication in rightauth, which allows the use
812: of different signature schemes for trustchain verification and authentication.
813:
814: - The initiator of an IKEv2 make-before-break reauthentication now suspends
815: online certificate revocation checks (OCSP, CRLs) until the new IKE_SA and all
816: CHILD_SAs are established. This is required if the checks are done over the
817: CHILD_SA established with the new IKE_SA. This is not possible until the
818: initiator installs this SA and that only happens after the authentication is
819: completed successfully. So we suspend the checks during the reauthentication
820: and do them afterwards, if they fail the IKE_SA is closed. This change has no
821: effect on the behavior during the authentication of the initial IKE_SA.
822:
823: - For the vici plugin a Vici:Session Perl CPAN module has been added to allow
824: Perl applications to control and/or monitor the IKE daemon using the VICI
825: interface, similar to the existing Python egg or Ruby gem.
826:
827: - Traffic selectors with port ranges can now be configured in the Linux kernel:
828: e.g. remote_ts = 10.1.0.0/16[tcp/20-23] local_ts = dynamic[tcp/32768-65535].
829: The port range must map to a port mask, though since the kernel does not
830: support arbitrary ranges.
831:
832: - The vici plugin allows the configuration of IPv4 and IPv6 address ranges
833: in local and remote traffic selectors. Since both the Linux kernel and
834: iptables cannot handle arbitrary ranges, address ranges are mapped to the next
835: larger CIDR subnet by the kernel-netlink and updown plugins, respectively.
836:
837: - Implemented IKEv1 IPv4/IPv6 address subnet and range identities that can be
838: used as owners of shared secrets.
839:
840:
841: strongswan-5.3.5
842: ----------------
843:
844: - Properly handle potential EINTR errors in sigwaitinfo(2) calls that replaced
845: sigwait(3) calls with 5.3.4.
846:
847: - RADIUS retransmission timeouts are now configurable, courtesy of Thom Troy.
848:
849:
850: strongswan-5.3.4
851: ----------------
852:
853: - Fixed an authentication bypass vulnerability in the eap-mschapv2 plugin that
854: was caused by insufficient verification of the internal state when handling
855: MSCHAPv2 Success messages received by the client.
856: This vulnerability has been registered as CVE-2015-8023.
857:
858: - The sha3 plugin implements the SHA3 Keccak-F1600 hash algorithm family.
859: Within the strongSwan framework SHA3 is currently used for BLISS signatures
860: only because the OIDs for other signature algorithms haven't been defined
861: yet. Also the use of SHA3 for IKEv2 has not been standardized yet.
862:
863:
864: strongswan-5.3.3
865: ----------------
866:
867: - Added support for the ChaCha20/Poly1305 AEAD cipher specified in RFC 7539 and
868: RFC 7634 using the chacha20poly1305 ike/esp proposal keyword. The new chapoly
869: plugin implements the cipher, if possible SSE-accelerated on x86/x64
870: architectures. It is usable both in IKEv2 and the strongSwan libipsec ESP
871: backend. On Linux 4.2 or newer the kernel-netlink plugin can configure the
872: cipher for ESP SAs.
873:
874: - The vici interface now supports the configuration of auxiliary certification
875: authority information as CRL and OCSP URIs.
876:
877: - In the bliss plugin the c_indices derivation using a SHA-512 based random
878: oracle has been fixed, generalized and standardized by employing the MGF1 mask
879: generation function with SHA-512. As a consequence BLISS signatures using the
880: improved oracle are not compatible with the earlier implementation.
881:
882: - Support for auto=route with right=%any for transport mode connections has
883: been added (the ikev2/trap-any scenario provides examples).
884:
885: - The starter daemon does not flush IPsec policies and SAs anymore when it is
886: stopped. Already existing duplicate policies are now overwritten by the IKE
887: daemon when it installs its policies.
888:
889: - Init limits (like charon.init_limit_half_open) can now optionally be enforced
890: when initiating SAs via VICI. For this, IKE_SAs initiated by the daemon are
891: now also counted as half-open SAs, which, as a side-effect, fixes the status
892: output while connecting (e.g. in ipsec status).
893:
894: - Symmetric configuration of EAP methods in left|rightauth is now possible when
895: mutual EAP-only authentication is used (previously, the client had to
896: configure rightauth=eap or rightauth=any, which prevented it from using this
897: same config as responder).
898:
899: - The initiator flag in the IKEv2 header is compared again (wasn't the case
900: since 5.0.0) and packets that have the flag set incorrectly are again ignored.
901:
902: - Implemented a demo Hardcopy Device IMC/IMV pair based on the "Hardcopy
903: Device Health Assessment Trusted Network Connect Binding" (HCD-TNC)
904: document drafted by the IEEE Printer Working Group (PWG).
905:
906: - Fixed IF-M segmentation which failed in the presence of multiple small
907: attributes in front of a huge attribute to be segmented.
908:
909:
910: strongswan-5.3.2
911: ----------------
912:
913: - Fixed a vulnerability that allowed rogue servers with a valid certificate
914: accepted by the client to trick it into disclosing its username and even
915: password (if the client accepts EAP-GTC). This was caused because constraints
916: against the responder's authentication were enforced too late.
917: This vulnerability has been registered as CVE-2015-4171.
918:
919:
920: strongswan-5.3.1
921: ----------------
922:
923: - Fixed a denial-of-service and potential remote code execution vulnerability
924: triggered by IKEv1/IKEv2 messages that contain payloads for the respective
925: other IKE version. Such payload are treated specially since 5.2.2 but because
926: they were still identified by their original payload type they were used as
927: such in some places causing invalid function pointer dereferences.
928: The vulnerability has been registered as CVE-2015-3991.
929:
930: - The new aesni plugin provides CBC, CTR, XCBC, CMAC, CCM and GCM crypto
931: primitives for AES-128/192/256. The plugin requires AES-NI and PCLMULQDQ
932: instructions and works on both x86 and x64 architectures. It provides
933: superior crypto performance in userland without any external libraries.
934:
935:
936: strongswan-5.3.0
937: ----------------
938:
939: - Added support for IKEv2 make-before-break reauthentication. By using a global
940: CHILD_SA reqid allocation mechanism, charon supports overlapping CHILD_SAs.
941: This allows the use of make-before-break instead of the previously supported
942: break-before-make reauthentication, avoiding connectivity gaps during that
943: procedure. As the new mechanism may fail with peers not supporting it (such
944: as any previous strongSwan release) it must be explicitly enabled using
945: the charon.make_before_break strongswan.conf option.
946:
947: - Support for "Signature Authentication in IKEv2" (RFC 7427) has been added.
948: This allows the use of stronger hash algorithms for public key authentication.
949: By default, signature schemes are chosen based on the strength of the
950: signature key, but specific hash algorithms may be configured in leftauth.
951:
952: - Key types and hash algorithms specified in rightauth are now also checked
953: against IKEv2 signature schemes. If such constraints are used for certificate
954: chain validation in existing configurations, in particular with peers that
955: don't support RFC 7427, it may be necessary to disable this feature with the
956: charon.signature_authentication_constraints setting, because the signature
957: scheme used in classic IKEv2 public key authentication may not be strong
958: enough.
959:
960: - The new connmark plugin allows a host to bind conntrack flows to a specific
961: CHILD_SA by applying and restoring the SA mark to conntrack entries. This
962: allows a peer to handle multiple transport mode connections coming over the
963: same NAT device for client-initiated flows. A common use case is to protect
964: L2TP/IPsec, as supported by some systems.
965:
966: - The forecast plugin can forward broadcast and multicast messages between
967: connected clients and a LAN. For CHILD_SA using unique marks, it sets up
968: the required Netfilter rules and uses a multicast/broadcast listener that
969: forwards such messages to all connected clients. This plugin is designed for
970: Windows 7 IKEv2 clients, which announces its services over the tunnel if the
971: negotiated IPsec policy allows it.
972:
973: - For the vici plugin a Python Egg has been added to allow Python applications
974: to control or monitor the IKE daemon using the VICI interface, similar to the
975: existing ruby gem. The Python library has been contributed by Björn Schuberg.
976:
977: - EAP server methods now can fulfill public key constraints, such as rightcert
978: or rightca. Additionally, public key and signature constraints can be
979: specified for EAP methods in the rightauth keyword. Currently the EAP-TLS and
980: EAP-TTLS methods provide verification details to constraints checking.
981:
982: - Upgrade of the BLISS post-quantum signature algorithm to the improved BLISS-B
983: variant. Can be used in conjunction with the SHA256, SHA384 and SHA512 hash
984: algorithms with SHA512 being the default.
985:
986: - The IF-IMV 1.4 interface now makes the IP address of the TNC access requestor
987: as seen by the TNC server available to all IMVs. This information can be
988: forwarded to policy enforcement points (e.g. firewalls or routers).
989:
990: - The new mutual tnccs-20 plugin parameter activates mutual TNC measurements
991: in PB-TNC half-duplex mode between two endpoints over either a PT-EAP or
992: PT-TLS transport medium.
993:
994:
995: strongswan-5.2.2
996: ----------------
997:
998: - Fixed a denial-of-service vulnerability triggered by an IKEv2 Key Exchange
999: payload that contains the Diffie-Hellman group 1025. This identifier was
1000: used internally for DH groups with custom generator and prime. Because
1001: these arguments are missing when creating DH objects based on the KE payload
1002: an invalid pointer dereference occurred. This allowed an attacker to crash
1003: the IKE daemon with a single IKE_SA_INIT message containing such a KE
1004: payload. The vulnerability has been registered as CVE-2014-9221.
1005:
1006: - The left/rightid options in ipsec.conf, or any other identity in strongSwan,
1007: now accept prefixes to enforce an explicit type, such as email: or fqdn:.
1008: Note that no conversion is done for the remaining string, refer to
1009: ipsec.conf(5) for details.
1010:
1011: - The post-quantum Bimodal Lattice Signature Scheme (BLISS) can be used as
1012: an IKEv2 public key authentication method. The pki tool offers full support
1013: for the generation of BLISS key pairs and certificates.
1014:
1015: - Fixed mapping of integrity algorithms negotiated for AH via IKEv1. This could
1016: cause interoperability issues when connecting to older versions of charon.
1017:
1018:
1019: strongswan-5.2.1
1020: ----------------
1021:
1022: - The new charon-systemd IKE daemon implements an IKE daemon tailored for use
1023: with systemd. It avoids the dependency on ipsec starter and uses swanctl
1024: as configuration backend, building a simple and lightweight solution. It
1025: supports native systemd journal logging.
1026:
1027: - Support for IKEv2 fragmentation as per RFC 7383 has been added. Like IKEv1
1028: fragmentation it can be enabled by setting fragmentation=yes in ipsec.conf.
1029:
1030: - Support of the TCG TNC IF-M Attribute Segmentation specification proposal.
1031: All attributes can be segmented. Additionally TCG/SWID Tag, TCG/SWID Tag ID
1032: and IETF/Installed Packages attributes can be processed incrementally on a
1033: per segment basis.
1034:
1035: - The new ext-auth plugin calls an external script to implement custom IKE_SA
1036: authorization logic, courtesy of Vyronas Tsingaras.
1037:
1038: - For the vici plugin a ruby gem has been added to allow ruby applications
1039: to control or monitor the IKE daemon. The vici documentation has been updated
1040: to include a description of the available operations and some simple examples
1041: using both the libvici C interface and the ruby gem.
1042:
1043:
1044: strongswan-5.2.0
1045: ----------------
1046:
1047: - strongSwan has been ported to the Windows platform. Using a MinGW toolchain,
1048: many parts of the strongSwan codebase run natively on Windows 7 / 2008 R2
1049: and newer releases. charon-svc implements a Windows IKE service based on
1050: libcharon, the kernel-iph and kernel-wfp plugins act as networking and IPsec
1051: backend on the Windows platform. socket-win provides a native IKE socket
1052: implementation, while winhttp fetches CRL and OCSP information using the
1053: WinHTTP API.
1054:
1055: - The new vici plugin provides a Versatile IKE Configuration Interface for
1056: charon. Using the stable IPC interface, external applications can configure,
1057: control and monitor the IKE daemon. Instead of scripting the ipsec tool
1058: and generating ipsec.conf, third party applications can use the new interface
1059: for more control and better reliability.
1060:
1061: - Built upon the libvici client library, swanctl implements the first user of
1062: the VICI interface. Together with a swanctl.conf configuration file,
1063: connections can be defined, loaded and managed. swanctl provides a portable,
1064: complete IKE configuration and control interface for the command line.
1065: The first six swanctl example scenarios have been added.
1066:
1067: - The SWID IMV implements a JSON-based REST API which allows the exchange
1068: of SWID tags and Software IDs with the strongTNC policy manager.
1069:
1070: - The SWID IMC can extract all installed packages from the dpkg (Debian,
1071: Ubuntu, Linux Mint etc.), rpm (Fedora, RedHat, OpenSUSE, etc.), or
1072: pacman (Arch Linux, Manjaro, etc.) package managers, respectively, using the
1073: swidGenerator (https://github.com/strongswan/swidGenerator) which generates
1074: SWID tags according to the new ISO/IEC 19770-2:2014 standard.
1075:
1076: - All IMVs now share the access requestor ID, device ID and product info
1077: of an access requestor via a common imv_session object.
1078:
1079: - The Attestation IMC/IMV pair supports the IMA-NG measurement format
1080: introduced with the Linux 3.13 kernel.
1081:
1082: - The aikgen tool generates an Attestation Identity Key bound to a TPM.
1083:
1084: - Implemented the PT-EAP transport protocol (RFC 7171) for Trusted Network
1085: Connect.
1086:
1087: - The ipsec.conf replay_window option defines connection specific IPsec replay
1088: windows. Original patch courtesy of Zheng Zhong and Christophe Gouault from
1089: 6Wind.
1090:
1091:
1092: strongswan-5.1.3
1093: ----------------
1094:
1095: - Fixed an authentication bypass vulnerability triggered by rekeying an
1096: unestablished IKEv2 SA while it gets actively initiated. This allowed an
1097: attacker to trick a peer's IKE_SA state to established, without the need to
1098: provide any valid authentication credentials. The vulnerability has been
1099: registered as CVE-2014-2338.
1100:
1101: - The acert plugin evaluates X.509 Attribute Certificates. Group membership
1102: information encoded as strings can be used to fulfill authorization checks
1103: defined with the rightgroups option. Attribute Certificates can be loaded
1104: locally or get exchanged in IKEv2 certificate payloads.
1105:
1106: - The pki command gained support to generate X.509 Attribute Certificates
1107: using the --acert subcommand, while the --print command supports the ac type.
1108: The openac utility has been removed in favor of the new pki functionality.
1109:
1110: - The libtls TLS 1.2 implementation as used by EAP-(T)TLS and other protocols
1111: has been extended by AEAD mode support, currently limited to AES-GCM.
1112:
1113:
1114: strongswan-5.1.2
1115: ----------------
1116:
1117: - A new default configuration file layout is introduced. The new default
1118: strongswan.conf file mainly includes config snippets from the strongswan.d
1119: and strongswan.d/charon directories (the latter containing snippets for all
1120: plugins). The snippets, with commented defaults, are automatically
1121: generated and installed, if they don't exist yet. They are also installed
1122: in $prefix/share/strongswan/templates so existing files can be compared to
1123: the current defaults.
1124:
1125: - As an alternative to the non-extensible charon.load setting, the plugins
1126: to load in charon (and optionally other applications) can now be determined
1127: via the charon.plugins.<name>.load setting for each plugin (enabled in the
1128: new default strongswan.conf file via the charon.load_modular option).
1129: The load setting optionally takes a numeric priority value that allows
1130: reordering the plugins (otherwise the default plugin order is preserved).
1131:
1132: - All strongswan.conf settings that were formerly defined in library specific
1133: "global" sections are now application specific (e.g. settings for plugins in
1134: libstrongswan.plugins can now be set only for charon in charon.plugins).
1135: The old options are still supported, which now allows to define defaults for
1136: all applications in the libstrongswan section.
1137:
1138: - The ntru libstrongswan plugin supports NTRUEncrypt as a post-quantum
1139: computer IKE key exchange mechanism. The implementation is based on the
1140: ntru-crypto library from the NTRUOpenSourceProject. The supported security
1141: strengths are ntru112, ntru128, ntru192, and ntru256. Since the private DH
1142: group IDs 1030..1033 have been assigned, the strongSwan Vendor ID must be
1143: sent (charon.send_vendor_id = yes) in order to use NTRU.
1144:
1145: - Defined a TPMRA remote attestation workitem and added support for it to the
1146: Attestation IMV.
1147:
1148: - Compatibility issues between IPComp (compress=yes) and leftfirewall=yes as
1149: well as multiple subnets in left|rightsubnet have been fixed.
1150:
1151: - When enabling its "session" strongswan.conf option, the xauth-pam plugin opens
1152: and closes a PAM session for each established IKE_SA. Patch courtesy of
1153: Andrea Bonomi.
1154:
1155: - The strongSwan unit testing framework has been rewritten without the "check"
1156: dependency for improved flexibility and portability. It now properly supports
1157: multi-threaded and memory leak testing and brings a bunch of new test cases.
1158:
1159:
1160: strongswan-5.1.1
1161: ----------------
1162:
1163: - Fixed a denial-of-service vulnerability and potential authorization bypass
1164: triggered by a crafted ID_DER_ASN1_DN ID payload. The cause is an insufficient
1165: length check when comparing such identities. The vulnerability has been
1166: registered as CVE-2013-6075.
1167:
1168: - Fixed a denial-of-service vulnerability triggered by a crafted IKEv1
1169: fragmentation payload. The cause is a NULL pointer dereference. The
1170: vulnerability has been registered as CVE-2013-6076.
1171:
1172: - The lean stand-alone pt-tls-client can set up a RFC 6876 PT-TLS session
1173: with a strongSwan policy enforcement point which uses the tnc-pdp charon
1174: plugin.
1175:
1176: - The new TCG TNC SWID IMC/IMV pair supports targeted SWID requests for either
1177: full SWID Tag or concise SWID Tag ID inventories.
1178:
1179: - The XAuth backend in eap-radius now supports multiple XAuth exchanges for
1180: different credential types and display messages. All user input gets
1181: concatenated and verified with a single User-Password RADIUS attribute on
1182: the AAA. With an AAA supporting it, one for example can implement
1183: Password+Token authentication with proper dialogs on iOS and OS X clients.
1184:
1185: - charon supports IKEv1 Mode Config exchange in push mode. The ipsec.conf
1186: modeconfig=push option enables it for both client and server, the same way
1187: as pluto used it.
1188:
1189: - Using the "ah" ipsec.conf keyword on both IKEv1 and IKEv2 connections,
1190: charon can negotiate and install Security Associations integrity-protected by
1191: the Authentication Header protocol. Supported are plain AH(+IPComp) SAs only,
1192: but not the deprecated RFC2401 style ESP+AH bundles.
1193:
1194: - The generation of initialization vectors for IKE and ESP (when using libipsec)
1195: is now modularized and IVs for e.g. AES-GCM are now correctly allocated
1196: sequentially, while other algorithms like AES-CBC still use random IVs.
1197:
1198: - The left and right options in ipsec.conf can take multiple address ranges
1199: and subnets. This allows connection matching against a larger set of
1200: addresses, for example to use a different connection for clients connecting
1201: from a internal network.
1202:
1203: - For all those who have a queasy feeling about the NIST elliptic curve set,
1204: the Brainpool curves introduced for use with IKE by RFC 6932 might be a
1205: more trustworthy alternative.
1206:
1207: - The kernel-libipsec userland IPsec backend now supports usage statistics,
1208: volume based rekeying and accepts ESPv3 style TFC padded packets.
1209:
1210: - With two new strongswan.conf options fwmarks can be used to implement
1211: host-to-host tunnels with kernel-libipsec.
1212:
1213: - load-tester supports transport mode connections and more complex traffic
1214: selectors, including such using unique ports for each tunnel.
1215:
1216: - The new dnscert plugin provides support for authentication via CERT RRs that
1217: are protected via DNSSEC. The plugin was created by Ruslan N. Marchenko.
1218:
1219: - The eap-radius plugin supports forwarding of several Cisco Unity specific
1220: RADIUS attributes in corresponding configuration payloads.
1221:
1222: - Database transactions are now abstracted and implemented by the two backends.
1223: If you use MySQL make sure all tables use the InnoDB engine.
1224:
1225: - libstrongswan now can provide an experimental custom implementation of the
1226: printf family functions based on klibc if neither Vstr nor glibc style printf
1227: hooks are available. This can avoid the Vstr dependency on some systems at
1228: the cost of slower and less complete printf functions.
1229:
1230:
1231: strongswan-5.1.0
1232: ----------------
1233:
1234: - Fixed a denial-of-service vulnerability triggered by specific XAuth usernames
1235: and EAP identities (since 5.0.3), and PEM files (since 4.1.11). The crash
1236: was caused by insufficient error handling in the is_asn1() function.
1237: The vulnerability has been registered as CVE-2013-5018.
1238:
1239: - The new charon-cmd command line IKE client can establish road warrior
1240: connections using IKEv1 or IKEv2 with different authentication profiles.
1241: It does not depend on any configuration files and can be configured using a
1242: few simple command line options.
1243:
1244: - The kernel-pfroute networking backend has been greatly improved. It now
1245: can install virtual IPs on TUN devices on OS X and FreeBSD, allowing these
1246: systems to act as a client in common road warrior scenarios.
1247:
1248: - The new kernel-libipsec plugin uses TUN devices and libipsec to provide IPsec
1249: processing in userland on Linux, FreeBSD and Mac OS X.
1250:
1251: - The eap-radius plugin can now serve as an XAuth backend called xauth-radius,
1252: directly verifying XAuth credentials using RADIUS User-Name/User-Password
1253: attributes. This is more efficient than the existing xauth-eap+eap-radius
1254: combination, and allows RADIUS servers without EAP support to act as AAA
1255: backend for IKEv1.
1256:
1257: - The new osx-attr plugin installs configuration attributes (currently DNS
1258: servers) via SystemConfiguration on Mac OS X. The keychain plugin provides
1259: certificates from the OS X keychain service.
1260:
1261: - The sshkey plugin parses SSH public keys, which, together with the --agent
1262: option for charon-cmd, allows the use of ssh-agent for authentication.
1263: To configure SSH keys in ipsec.conf the left|rightrsasigkey options are
1264: replaced with left|rightsigkey, which now take public keys in one of three
1265: formats: SSH (RFC 4253, ssh: prefix), DNSKEY (RFC 3110, dns: prefix), and
1266: PKCS#1 (the default, no prefix).
1267:
1268: - Extraction of certificates and private keys from PKCS#12 files is now provided
1269: by the new pkcs12 plugin or the openssl plugin. charon-cmd (--p12) as well
1270: as charon (via P12 token in ipsec.secrets) can make use of this.
1271:
1272: - IKEv2 can now negotiate transport mode and IPComp in NAT situations.
1273:
1274: - IKEv2 exchange initiators now properly close an established IKE or CHILD_SA
1275: on error conditions using an additional exchange, keeping state in sync
1276: between peers.
1277:
1278: - Using a SQL database interface a Trusted Network Connect (TNC) Policy Manager
1279: can generate specific measurement workitems for an arbitrary number of
1280: Integrity Measurement Verifiers (IMVs) based on the history of the VPN user
1281: and/or device.
1282:
1283: - Several core classes in libstrongswan are now tested with unit tests. These
1284: can be enabled with --enable-unit-tests and run with 'make check'. Coverage
1285: reports can be generated with --enable-coverage and 'make coverage' (this
1286: disables any optimization, so it should not be enabled when building
1287: production releases).
1288:
1289: - The leak-detective developer tool has been greatly improved. It works much
1290: faster/stabler with multiple threads, does not use deprecated malloc hooks
1291: anymore and has been ported to OS X.
1292:
1293: - chunk_hash() is now based on SipHash-2-4 with a random key. This provides
1294: better distribution and prevents hash flooding attacks when used with
1295: hashtables.
1296:
1297: - All default plugins implement the get_features() method to define features
1298: and their dependencies. The plugin loader has been improved, so that plugins
1299: in a custom load statement can be ordered freely or to express preferences
1300: without being affected by dependencies between plugin features.
1301:
1302: - A centralized thread can take care for watching multiple file descriptors
1303: concurrently. This removes the need for a dedicated listener threads in
1304: various plugins. The number of "reserved" threads for such tasks has been
1305: reduced to about five, depending on the plugin configuration.
1306:
1307: - Plugins that can be controlled by a UNIX socket IPC mechanism gained network
1308: transparency. Third party applications querying these plugins now can use
1309: TCP connections from a different host.
1310:
1311: - libipsec now supports AES-GCM.
1312:
1313:
1314: strongswan-5.0.4
1315: ----------------
1316:
1317: - Fixed a security vulnerability in the openssl plugin which was reported by
1318: Kevin Wojtysiak. The vulnerability has been registered as CVE-2013-2944.
1319: Before the fix, if the openssl plugin's ECDSA signature verification was used,
1320: due to a misinterpretation of the error code returned by the OpenSSL
1321: ECDSA_verify() function, an empty or zeroed signature was accepted as a
1322: legitimate one.
1323:
1324: - The handling of a couple of other non-security relevant openssl return codes
1325: was fixed as well.
1326:
1327: - The tnc_ifmap plugin now publishes virtual IPv4 and IPv6 addresses via its
1328: TCG TNC IF-MAP 2.1 interface.
1329:
1330: - The charon.initiator_only option causes charon to ignore IKE initiation
1331: requests.
1332:
1333: - The openssl plugin can now use the openssl-fips library.
1334:
1335:
1336: strongswan-5.0.3
1337: ----------------
1338:
1339: - The new ipseckey plugin enables authentication based on trustworthy public
1340: keys stored as IPSECKEY resource records in the DNS and protected by DNSSEC.
1341: To do so it uses a DNSSEC enabled resolver, like the one provided by the new
1342: unbound plugin, which is based on libldns and libunbound. Both plugins were
1343: created by Reto Guadagnini.
1344:
1345: - Implemented the TCG TNC IF-IMV 1.4 draft making access requestor identities
1346: available to an IMV. The OS IMV stores the AR identity together with the
1347: device ID in the attest database.
1348:
1349: - The openssl plugin now uses the AES-NI accelerated version of AES-GCM
1350: if the hardware supports it.
1351:
1352: - The eap-radius plugin can now assign virtual IPs to IKE clients using the
1353: Framed-IP-Address attribute by using the "%radius" named pool in the
1354: rightsourceip ipsec.conf option. Cisco Banner attributes are forwarded to
1355: Unity-capable IKEv1 clients during mode config. charon now sends Interim
1356: Accounting updates if requested by the RADIUS server, reports
1357: sent/received packets in Accounting messages, and adds a Terminate-Cause
1358: to Accounting-Stops.
1359:
1360: - The recently introduced "ipsec listcounters" command can report connection
1361: specific counters by passing a connection name, and global or connection
1362: counters can be reset by the "ipsec resetcounters" command.
1363:
1364: - The strongSwan libpttls library provides an experimental implementation of
1365: PT-TLS (RFC 6876), a Posture Transport Protocol over TLS.
1366:
1367: - The charon systime-fix plugin can disable certificate lifetime checks on
1368: embedded systems if the system time is obviously out of sync after bootup.
1369: Certificates lifetimes get checked once the system time gets sane, closing
1370: or reauthenticating connections using expired certificates.
1371:
1372: - The "ikedscp" ipsec.conf option can set DiffServ code points on outgoing
1373: IKE packets.
1374:
1375: - The new xauth-noauth plugin allows to use basic RSA or PSK authentication with
1376: clients that cannot be configured without XAuth authentication. The plugin
1377: simply concludes the XAuth exchange successfully without actually performing
1378: any authentication. Therefore, to use this backend it has to be selected
1379: explicitly with rightauth2=xauth-noauth.
1380:
1381: - The new charon-tkm IKEv2 daemon delegates security critical operations to a
1382: separate process. This has the benefit that the network facing daemon has no
1383: knowledge of keying material used to protect child SAs. Thus subverting
1384: charon-tkm does not result in the compromise of cryptographic keys.
1385: The extracted functionality has been implemented from scratch in a minimal TCB
1386: (trusted computing base) in the Ada programming language. Further information
1387: can be found at https://www.codelabs.ch/tkm/.
1388:
1389: strongswan-5.0.2
1390: ----------------
1391:
1392: - Implemented all IETF Standard PA-TNC attributes and an OS IMC/IMV
1393: pair using them to transfer operating system information.
1394:
1395: - The new "ipsec listcounters" command prints a list of global counter values
1396: about received and sent IKE messages and rekeyings.
1397:
1398: - A new lookip plugin can perform fast lookup of tunnel information using a
1399: clients virtual IP and can send notifications about established or deleted
1400: tunnels. The "ipsec lookip" command can be used to query such information
1401: or receive notifications.
1402:
1403: - The new error-notify plugin catches some common error conditions and allows
1404: an external application to receive notifications for them over a UNIX socket.
1405:
1406: - IKE proposals can now use a PRF algorithm different to that defined for
1407: integrity protection. If an algorithm with a "prf" prefix is defined
1408: explicitly (such as prfsha1 or prfsha256), no implicit PRF algorithm based on
1409: the integrity algorithm is added to the proposal.
1410:
1411: - The pkcs11 plugin can now load leftcert certificates from a smartcard for a
1412: specific ipsec.conf conn section and cacert CA certificates for a specific ca
1413: section.
1414:
1415: - The load-tester plugin gained additional options for certificate generation
1416: and can load keys and multiple CA certificates from external files. It can
1417: install a dedicated outer IP address for each tunnel and tunnel initiation
1418: batches can be triggered and monitored externally using the
1419: "ipsec load-tester" tool.
1420:
1421: - PKCS#7 container parsing has been modularized, and the openssl plugin
1422: gained an alternative implementation to decrypt and verify such files.
1423: In contrast to our own DER parser, OpenSSL can handle BER files, which is
1424: required for interoperability of our scepclient with EJBCA.
1425:
1426: - Support for the proprietary IKEv1 fragmentation extension has been added.
1427: Fragments are always handled on receipt but only sent if supported by the peer
1428: and if enabled with the new fragmentation ipsec.conf option.
1429:
1430: - IKEv1 in charon can now parse certificates received in PKCS#7 containers and
1431: supports NAT traversal as used by Windows clients. Patches courtesy of
1432: Volker Rümelin.
1433:
1434: - The new rdrand plugin provides a high quality / high performance random
1435: source using the Intel rdrand instruction found on Ivy Bridge processors.
1436:
1437: - The integration test environment was updated and now uses KVM and reproducible
1438: guest images based on Debian.
1439:
1440:
1441: strongswan-5.0.1
1442: ----------------
1443:
1444: - Introduced the sending of the standard IETF Assessment Result
1445: PA-TNC attribute by all strongSwan Integrity Measurement Verifiers.
1446:
1447: - Extended PTS Attestation IMC/IMV pair to provide full evidence of
1448: the Linux IMA measurement process. All pertinent file information
1449: of a Linux OS can be collected and stored in an SQL database.
1450:
1451: - The PA-TNC and PB-TNC protocols can now process huge data payloads
1452: >64 kB by distributing PA-TNC attributes over multiple PA-TNC messages
1453: and these messages over several PB-TNC batches. As long as no
1454: consolidated recommendation from all IMVs can be obtained, the TNC
1455: server requests more client data by sending an empty SDATA batch.
1456:
1457: - The rightgroups2 ipsec.conf option can require group membership during
1458: a second authentication round, for example during XAuth authentication
1459: against a RADIUS server.
1460:
1461: - The xauth-pam backend can authenticate IKEv1 XAuth and Hybrid authenticated
1462: clients against any PAM service. The IKEv2 eap-gtc plugin does not use
1463: PAM directly anymore, but can use any XAuth backend to verify credentials,
1464: including xauth-pam.
1465:
1466: - The new unity plugin brings support for some parts of the IKEv1 Cisco Unity
1467: Extension. As client, charon narrows traffic selectors to the received
1468: Split-Include attributes and automatically installs IPsec bypass policies
1469: for received Local-LAN attributes. As server, charon sends Split-Include
1470: attributes for leftsubnet definitions containing multiple subnets to Unity-
1471: aware clients.
1472:
1473: - An EAP-Nak payload is returned by clients if the gateway requests an EAP
1474: method that the client does not support. Clients can also request a specific
1475: EAP method by configuring that method with leftauth.
1476:
1477: - The eap-dynamic plugin handles EAP-Nak payloads returned by clients and uses
1478: these to select a different EAP method supported/requested by the client.
1479: The plugin initially requests the first registered method or the first method
1480: configured with charon.plugins.eap-dynamic.preferred.
1481:
1482: - The new left/rightdns options specify connection specific DNS servers to
1483: request/respond in IKEv2 configuration payloads or IKEv2 mode config. leftdns
1484: can be any (comma separated) combination of %config4 and %config6 to request
1485: multiple servers, both for IPv4 and IPv6. rightdns takes a list of DNS server
1486: IP addresses to return.
1487:
1488: - The left/rightsourceip options now accept multiple addresses or pools.
1489: leftsourceip can be any (comma separated) combination of %config4, %config6
1490: or fixed IP addresses to request. rightsourceip accepts multiple explicitly
1491: specified or referenced named pools.
1492:
1493: - Multiple connections can now share a single address pool when they use the
1494: same definition in one of the rightsourceip pools.
1495:
1496: - The options charon.interfaces_ignore and charon.interfaces_use allow one to
1497: configure the network interfaces used by the daemon.
1498:
1499: - The kernel-netlink plugin supports the charon.install_virtual_ip_on option,
1500: which specifies the interface on which virtual IP addresses will be installed.
1501: If it is not specified the current behavior of using the outbound interface
1502: is preserved.
1503:
1504: - The kernel-netlink plugin tries to keep the current source address when
1505: looking for valid routes to reach other hosts.
1506:
1507: - The autotools build has been migrated to use a config.h header. strongSwan
1508: development headers will get installed during "make install" if
1509: --with-dev-headers has been passed to ./configure.
1510:
1511: - All crypto primitives gained return values for most operations, allowing
1512: crypto backends to fail, for example when using hardware accelerators.
1513:
1514:
1515: strongswan-5.0.0
1516: ----------------
1517:
1518: - The charon IKE daemon gained experimental support for the IKEv1 protocol.
1519: Pluto has been removed from the 5.x series, and unless strongSwan is
1520: configured with --disable-ikev1 or --disable-ikev2, charon handles both
1521: keying protocols. The feature-set of IKEv1 in charon is almost on par with
1522: pluto, but currently does not support AH or bundled AH+ESP SAs. Beside
1523: RSA/ECDSA, PSK and XAuth, charon also supports the Hybrid authentication
1524: mode. Information for interoperability and migration is available at
1525: https://wiki.strongswan.org/projects/strongswan/wiki/CharonPlutoIKEv1.
1526:
1527: - Charon's bus_t has been refactored so that loggers and other listeners are
1528: now handled separately. The single lock was previously cause for deadlocks
1529: if extensive listeners, such as the one provided by the updown plugin, wanted
1530: to acquire locks that were held by other threads which in turn tried to log
1531: messages, and thus were waiting to acquire the same lock currently held by
1532: the thread calling the listener.
1533: The implemented changes also allow the use of a read/write-lock for the
1534: loggers which increases performance if multiple loggers are registered.
1535: Besides several interface changes this last bit also changes the semantics
1536: for loggers as these may now be called by multiple threads at the same time.
1537:
1538: - Source routes are reinstalled if interfaces are reactivated or IP addresses
1539: reappear.
1540:
1541: - The thread pool (processor_t) now has more control over the lifecycle of
1542: a job (see job.h for details). In particular, it now controls the destruction
1543: of jobs after execution and the cancellation of jobs during shutdown. Due to
1544: these changes the requeueing feature, previously available to callback_job_t
1545: only, is now available to all jobs (in addition to a new rescheduling
1546: feature).
1547:
1548: - In addition to trustchain key strength definitions for different public key
1549: systems, the rightauth option now takes a list of signature hash algorithms
1550: considered save for trustchain validation. For example, the setting
1551: rightauth=rsa-2048-ecdsa-256-sha256-sha384-sha512 requires a trustchain
1552: that uses at least RSA-2048 or ECDSA-256 keys and certificate signatures
1553: using SHA-256 or better.
1554:
1555:
1556: strongswan-4.6.4
1557: ----------------
1558:
1559: - Fixed a security vulnerability in the gmp plugin. If this plugin was used
1560: for RSA signature verification an empty or zeroed signature was handled as
1561: a legitimate one.
1562:
1563: - Fixed several issues with reauthentication and address updates.
1564:
1565:
1566: strongswan-4.6.3
1567: ----------------
1568:
1569: - The tnc-pdp plugin implements a RADIUS server interface allowing
1570: a strongSwan TNC server to act as a Policy Decision Point.
1571:
1572: - The eap-radius authentication backend enforces Session-Timeout attributes
1573: using RFC4478 repeated authentication and acts upon RADIUS Dynamic
1574: Authorization extensions, RFC 5176. Currently supported are disconnect
1575: requests and CoA messages containing a Session-Timeout.
1576:
1577: - The eap-radius plugin can forward arbitrary RADIUS attributes from and to
1578: clients using custom IKEv2 notify payloads. The new radattr plugin reads
1579: attributes to include from files and prints received attributes to the
1580: console.
1581:
1582: - Added support for untruncated MD5 and SHA1 HMACs in ESP as used in
1583: RFC 4595.
1584:
1585: - The cmac plugin implements the AES-CMAC-96 and AES-CMAC-PRF-128 algorithms
1586: as defined in RFC 4494 and RFC 4615, respectively.
1587:
1588: - The resolve plugin automatically installs nameservers via resolvconf(8),
1589: if it is installed, instead of modifying /etc/resolv.conf directly.
1590:
1591: - The IKEv2 charon daemon supports now raw RSA public keys in RFC 3110
1592: DNSKEY and PKCS#1 file format.
1593:
1594:
1595: strongswan-4.6.2
1596: ----------------
1597:
1598: - Upgraded the TCG IF-IMC and IF-IMV C API to the upcoming version 1.3
1599: which supports IF-TNCCS 2.0 long message types, the exclusive flags
1600: and multiple IMC/IMV IDs. Both the TNC Client and Server as well as
1601: the "Test", "Scanner", and "Attestation" IMC/IMV pairs were updated.
1602:
1603: - Fully implemented the "TCG Attestation PTS Protocol: Binding to IF-M"
1604: standard (TLV-based messages only). TPM-based remote attestation of
1605: Linux IMA (Integrity Measurement Architecture) possible. Measurement
1606: reference values are automatically stored in an SQLite database.
1607:
1608: - The EAP-RADIUS authentication backend supports RADIUS accounting. It sends
1609: start/stop messages containing Username, Framed-IP and Input/Output-Octets
1610: attributes and has been tested against FreeRADIUS and Microsoft NPS.
1611:
1612: - Added support for PKCS#8 encoded private keys via the libstrongswan
1613: pkcs8 plugin. This is the default format used by some OpenSSL tools since
1614: version 1.0.0 (e.g. openssl req with -keyout).
1615:
1616: - Added session resumption support to the strongSwan TLS stack.
1617:
1618:
1619: strongswan-4.6.1
1620: ----------------
1621:
1622: - Because of changing checksums before and after installation which caused
1623: the integrity tests to fail we avoided directly linking libsimaka, libtls and
1624: libtnccs to those libcharon plugins which make use of these dynamic libraries.
1625: Instead we linked the libraries to the charon daemon. Unfortunately Ubuntu
1626: 11.10 activated the --as-needed ld option which discards explicit links
1627: to dynamic libraries that are not actually used by the charon daemon itself,
1628: thus causing failures during the loading of the plugins which depend on these
1629: libraries for resolving external symbols.
1630:
1631: - Therefore our approach of computing integrity checksums for plugins had to be
1632: changed radically by moving the hash generation from the compilation to the
1633: post-installation phase.
1634:
1635:
1636: strongswan-4.6.0
1637: ----------------
1638:
1639: - The new libstrongswan certexpire plugin collects expiration information of
1640: all used certificates and exports them to CSV files. It either directly
1641: exports them or uses cron style scheduling for batch exports.
1642:
1643: - starter passes unresolved hostnames to charon, allowing it to do name
1644: resolution not before the connection attempt. This is especially useful with
1645: connections between hosts using dynamic IP addresses. Thanks to Mirko Parthey
1646: for the initial patch.
1647:
1648: - The android plugin can now be used without the Android frontend patch and
1649: provides DNS server registration and logging to logcat.
1650:
1651: - Pluto and starter (plus stroke and whack) have been ported to Android.
1652:
1653: - Support for ECDSA private and public key operations has been added to the
1654: pkcs11 plugin. The plugin now also provides DH and ECDH via PKCS#11 and can
1655: use tokens as random number generators (RNG). By default only private key
1656: operations are enabled, more advanced features have to be enabled by their
1657: option in strongswan.conf. This also applies to public key operations (even
1658: for keys not stored on the token) which were enabled by default before.
1659:
1660: - The libstrongswan plugin system now supports detailed plugin dependencies.
1661: Many plugins have been extended to export its capabilities and requirements.
1662: This allows the plugin loader to resolve plugin loading order automatically,
1663: and in future releases, to dynamically load the required features on demand.
1664: Existing third party plugins are source (but not binary) compatible if they
1665: properly initialize the new get_features() plugin function to NULL.
1666:
1667: - The tnc-ifmap plugin implements a TNC IF-MAP 2.0 client which can deliver
1668: metadata about IKE_SAs via a SOAP interface to a MAP server. The tnc-ifmap
1669: plugin requires the Apache Axis2/C library.
1670:
1671:
1672: strongswan-4.5.3
1673: ----------------
1674:
1675: - Our private libraries (e.g. libstrongswan) are not installed directly in
1676: prefix/lib anymore. Instead a subdirectory is used (prefix/lib/ipsec/ by
1677: default). The plugins directory is also moved from libexec/ipsec/ to that
1678: directory.
1679:
1680: - The dynamic IMC/IMV libraries were moved from the plugins directory to
1681: a new imcvs directory in the prefix/lib/ipsec/ subdirectory.
1682:
1683: - Job priorities were introduced to prevent thread starvation caused by too
1684: many threads handling blocking operations (such as CRL fetching). Refer to
1685: strongswan.conf(5) for details.
1686:
1687: - Two new strongswan.conf options allow to fine-tune performance on IKEv2
1688: gateways by dropping IKE_SA_INIT requests on high load.
1689:
1690: - IKEv2 charon daemon supports start PASS and DROP shunt policies
1691: preventing traffic to go through IPsec connections. Installation of the
1692: shunt policies either via the XFRM netfilter or PFKEYv2 IPsec kernel
1693: interfaces.
1694:
1695: - The history of policies installed in the kernel is now tracked so that e.g.
1696: trap policies are correctly updated when reauthenticated SAs are terminated.
1697:
1698: - IMC/IMV Scanner pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1699: Using "netstat -l" the IMC scans open listening ports on the TNC client
1700: and sends a port list to the IMV which based on a port policy decides if
1701: the client is admitted to the network.
1702: (--enable-imc-scanner/--enable-imv-scanner).
1703:
1704: - IMC/IMV Test pair implementing the RFC 5792 PA-TNC (IF-M) protocol.
1705: (--enable-imc-test/--enable-imv-test).
1706:
1707: - The IKEv2 close action does not use the same value as the ipsec.conf dpdaction
1708: setting, but the value defined by its own closeaction keyword. The action
1709: is triggered if the remote peer closes a CHILD_SA unexpectedly.
1710:
1711:
1712: strongswan-4.5.2
1713: ----------------
1714:
1715: - The whitelist plugin for the IKEv2 daemon maintains an in-memory identity
1716: whitelist. Any connection attempt of peers not whitelisted will get rejected.
1717: The 'ipsec whitelist' utility provides a simple command line frontend for
1718: whitelist administration.
1719:
1720: - The duplicheck plugin provides a specialized form of duplicate checking,
1721: doing a liveness check on the old SA and optionally notify a third party
1722: application about detected duplicates.
1723:
1724: - The coupling plugin permanently couples two or more devices by limiting
1725: authentication to previously used certificates.
1726:
1727: - In the case that the peer config and child config don't have the same name
1728: (usually in SQL database defined connections), ipsec up|route <peer config>
1729: starts|routes all associated child configs and ipsec up|route <child config>
1730: only starts|routes the specific child config.
1731:
1732: - fixed the encoding and parsing of X.509 certificate policy statements (CPS).
1733:
1734: - Duncan Salerno contributed the eap-sim-pcsc plugin implementing a
1735: pcsc-lite based SIM card backend.
1736:
1737: - The eap-peap plugin implements the EAP PEAP protocol. Interoperates
1738: successfully with a FreeRADIUS server and Windows 7 Agile VPN clients.
1739:
1740: - The IKEv2 daemon charon rereads strongswan.conf on SIGHUP and instructs
1741: all plugins to reload. Currently only the eap-radius and the attr plugins
1742: support configuration reloading.
1743:
1744: - Added userland support to the IKEv2 daemon for Extended Sequence Numbers
1745: support coming with Linux 2.6.39. To enable ESN on a connection, add
1746: the 'esn' keyword to the proposal. The default proposal uses 32-bit sequence
1747: numbers only ('noesn'), and the same value is used if no ESN mode is
1748: specified. To negotiate ESN support with the peer, include both, e.g.
1749: esp=aes128-sha1-esn-noesn.
1750:
1751: - In addition to ESN, Linux 2.6.39 gained support for replay windows larger
1752: than 32 packets. The new global strongswan.conf option 'charon.replay_window'
1753: configures the size of the replay window, in packets.
1754:
1755:
1756: strongswan-4.5.1
1757: ----------------
1758:
1759: - Sansar Choinyambuu implemented the RFC 5793 Posture Broker Protocol (BP)
1760: compatible with Trusted Network Connect (TNC). The TNCCS 2.0 protocol
1761: requires the tnccs_20, tnc_imc and tnc_imv plugins but does not depend
1762: on the libtnc library. Any available IMV/IMC pairs conforming to the
1763: Trusted Computing Group's TNC-IF-IMV/IMC 1.2 interface specification
1764: can be loaded via /etc/tnc_config.
1765:
1766: - Re-implemented the TNCCS 1.1 protocol by using the tnc_imc and tnc_imv
1767: in place of the external libtnc library.
1768:
1769: - The tnccs_dynamic plugin loaded on a TNC server in addition to the
1770: tnccs_11 and tnccs_20 plugins, dynamically detects the IF-TNCCS
1771: protocol version used by a TNC client and invokes an instance of
1772: the corresponding protocol stack.
1773:
1774: - IKE and ESP proposals can now be stored in an SQL database using a
1775: new proposals table. The start_action field in the child_configs
1776: tables allows the automatic starting or routing of connections stored
1777: in an SQL database.
1778:
1779: - The new certificate_authorities and certificate_distribution_points
1780: tables make it possible to store CRL and OCSP Certificate Distribution
1781: points in an SQL database.
1782:
1783: - The new 'include' statement allows to recursively include other files in
1784: strongswan.conf. Existing sections and values are thereby extended and
1785: replaced, respectively.
1786:
1787: - Due to the changes in the parser for strongswan.conf, the configuration
1788: syntax for the attr plugin has changed. Previously, it was possible to
1789: specify multiple values of a specific attribute type by adding multiple
1790: key/value pairs with the same key (e.g. dns) to the plugins.attr section.
1791: Because values with the same key now replace previously defined values
1792: this is not possible anymore. As an alternative, multiple values can be
1793: specified by separating them with a comma (e.g. dns = 1.2.3.4, 2.3.4.5).
1794:
1795: - ipsec listalgs now appends (set in square brackets) to each crypto
1796: algorithm listed the plugin that registered the function.
1797:
1798: - Traffic Flow Confidentiality padding supported with Linux 2.6.38 can be used
1799: by the IKEv2 daemon. The ipsec.conf 'tfc' keyword pads all packets to a given
1800: boundary, the special value '%mtu' pads all packets to the path MTU.
1801:
1802: - The new af-alg plugin can use various crypto primitives of the Linux Crypto
1803: API using the AF_ALG interface introduced with 2.6.38. This removes the need
1804: for additional userland implementations of symmetric cipher, hash, hmac and
1805: xcbc algorithms.
1806:
1807: - The IKEv2 daemon supports the INITIAL_CONTACT notify as initiator and
1808: responder. The notify is sent when initiating configurations with a unique
1809: policy, set in ipsec.conf via the global 'uniqueids' option.
1810:
1811: - The conftest conformance testing framework enables the IKEv2 stack to perform
1812: many tests using a distinct tool and configuration frontend. Various hooks
1813: can alter reserved bits, flags, add custom notifies and proposals, reorder
1814: or drop messages and much more. It is enabled using the --enable-conftest
1815: ./configure switch.
1816:
1817: - The new libstrongswan constraints plugin provides advanced X.509 constraint
1818: checking. In addition to X.509 pathLen constraints, the plugin checks for
1819: nameConstraints and certificatePolicies, including policyMappings and
1820: policyConstraints. The x509 certificate plugin and the pki tool have been
1821: enhanced to support these extensions. The new left/rightcertpolicy ipsec.conf
1822: connection keywords take OIDs a peer certificate must have.
1823:
1824: - The left/rightauth ipsec.conf keywords accept values with a minimum strength
1825: for trustchain public keys in bits, such as rsa-2048 or ecdsa-256.
1826:
1827: - The revocation and x509 libstrongswan plugins and the pki tool gained basic
1828: support for delta CRLs.
1829:
1830:
1831: strongswan-4.5.0
1832: ----------------
1833:
1834: - IMPORTANT: the default keyexchange mode 'ike' is changing with release 4.5
1835: from 'ikev1' to 'ikev2', thus commemorating the five year anniversary of the
1836: IKEv2 RFC 4306 and its mature successor RFC 5996. The time has definitively
1837: come for IKEv1 to go into retirement and to cede its place to the much more
1838: robust, powerful and versatile IKEv2 protocol!
1839:
1840: - Added new ctr, ccm and gcm plugins providing Counter, Counter with CBC-MAC
1841: and Galois/Counter Modes based on existing CBC implementations. These
1842: new plugins bring support for AES and Camellia Counter and CCM algorithms
1843: and the AES GCM algorithms for use in IKEv2.
1844:
1845: - The new pkcs11 plugin brings full Smartcard support to the IKEv2 daemon and
1846: the pki utility using one or more PKCS#11 libraries. It currently supports
1847: RSA private and public key operations and loads X.509 certificates from
1848: tokens.
1849:
1850: - Implemented a general purpose TLS stack based on crypto and credential
1851: primitives of libstrongswan. libtls supports TLS versions 1.0, 1.1 and 1.2,
1852: ECDHE-ECDSA/RSA, DHE-RSA and RSA key exchange algorithms and RSA/ECDSA based
1853: client authentication.
1854:
1855: - Based on libtls, the eap-tls plugin brings certificate based EAP
1856: authentication for client and server. It is compatible to Windows 7 IKEv2
1857: Smartcard authentication and the OpenSSL based FreeRADIUS EAP-TLS backend.
1858:
1859: - Implemented the TNCCS 1.1 Trusted Network Connect protocol using the
1860: libtnc library on the strongSwan client and server side via the tnccs_11
1861: plugin and optionally connecting to a TNC@FHH-enhanced FreeRADIUS AAA server.
1862: Depending on the resulting TNC Recommendation, strongSwan clients are granted
1863: access to a network behind a strongSwan gateway (allow), are put into a
1864: remediation zone (isolate) or are blocked (none), respectively. Any number
1865: of Integrity Measurement Collector/Verifier pairs can be attached
1866: via the tnc-imc and tnc-imv charon plugins.
1867:
1868: - The IKEv1 daemon pluto now uses the same kernel interfaces as the IKEv2
1869: daemon charon. As a result of this, pluto now supports xfrm marks which
1870: were introduced in charon with 4.4.1.
1871:
1872: - Applets for Maemo 5 (Nokia) allow to easily configure and control IKEv2
1873: based VPN connections with EAP authentication on supported devices.
1874:
1875: - The RADIUS plugin eap-radius now supports multiple RADIUS servers for
1876: redundant setups. Servers are selected by a defined priority, server load and
1877: availability.
1878:
1879: - The simple led plugin controls hardware LEDs through the Linux LED subsystem.
1880: It currently shows activity of the IKE daemon and is a good example how to
1881: implement a simple event listener.
1882:
1883: - Improved MOBIKE behavior in several corner cases, for instance, if the
1884: initial responder moves to a different address.
1885:
1886: - Fixed left-/rightnexthop option, which was broken since 4.4.0.
1887:
1888: - Fixed a bug not releasing a virtual IP address to a pool if the XAUTH
1889: identity was different from the IKE identity.
1890:
1891: - Fixed the alignment of ModeConfig messages on 4-byte boundaries in the
1892: case where the attributes are not a multiple of 4 bytes (e.g. Cisco's
1893: UNITY_BANNER).
1894:
1895: - Fixed the interoperability of the socket_raw and socket_default
1896: charon plugins.
1897:
1898: - Added man page for strongswan.conf
1899:
1900:
1901: strongswan-4.4.1
1902: ----------------
1903:
1904: - Support of xfrm marks in IPsec SAs and IPsec policies introduced
1905: with the Linux 2.6.34 kernel. For details see the example scenarios
1906: ikev2/nat-two-rw-mark, ikev2/rw-nat-mark-in-out and ikev2/net2net-psk-dscp.
1907:
1908: - The PLUTO_MARK_IN and PLUTO_ESP_ENC environment variables can be used
1909: in a user-specific updown script to set marks on inbound ESP or
1910: ESP_IN_UDP packets.
1911:
1912: - The openssl plugin now supports X.509 certificate and CRL functions.
1913:
1914: - OCSP/CRL checking in IKEv2 has been moved to the revocation plugin, enabled
1915: by default. Please update manual load directives in strongswan.conf.
1916:
1917: - RFC3779 ipAddrBlock constraint checking has been moved to the addrblock
1918: plugin, disabled by default. Enable it and update manual load directives
1919: in strongswan.conf, if required.
1920:
1921: - The pki utility supports CRL generation using the --signcrl command.
1922:
1923: - The ipsec pki --self, --issue and --req commands now support output in
1924: PEM format using the --outform pem option.
1925:
1926: - The major refactoring of the IKEv1 Mode Config functionality now allows
1927: the transport and handling of any Mode Config attribute.
1928:
1929: - The RADIUS proxy plugin eap-radius now supports multiple servers. Configured
1930: servers are chosen randomly, with the option to prefer a specific server.
1931: Non-responding servers are degraded by the selection process.
1932:
1933: - The ipsec pool tool manages arbitrary configuration attributes stored
1934: in an SQL database. ipsec pool --help gives the details.
1935:
1936: - The new eap-simaka-sql plugin acts as a backend for EAP-SIM and EAP-AKA,
1937: reading triplets/quintuplets from an SQL database.
1938:
1939: - The High Availability plugin now supports a HA enabled in-memory address
1940: pool and Node reintegration without IKE_SA rekeying. The latter allows
1941: clients without IKE_SA rekeying support to keep connected during
1942: reintegration. Additionally, many other issues have been fixed in the ha
1943: plugin.
1944:
1945: - Fixed a potential remote code execution vulnerability resulting from
1946: the misuse of snprintf(). The vulnerability is exploitable by
1947: unauthenticated users.
1948:
1949:
1950: strongswan-4.4.0
1951: ----------------
1952:
1953: - The IKEv2 High Availability plugin has been integrated. It provides
1954: load sharing and failover capabilities in a cluster of currently two nodes,
1955: based on an extend ClusterIP kernel module. More information is available at
1956: https://wiki.strongswan.org/projects/strongswan/wiki/HighAvailability.
1957: The development of the High Availability functionality was sponsored by
1958: secunet Security Networks AG.
1959:
1960: - Added IKEv1 and IKEv2 configuration support for the AES-GMAC
1961: authentication-only ESP cipher. Our aes_gmac kernel patch or a Linux
1962: 2.6.34 kernel is required to make AES-GMAC available via the XFRM
1963: kernel interface.
1964:
1965: - Added support for Diffie-Hellman groups 22, 23 and 24 to the gmp, gcrypt
1966: and openssl plugins, usable by both pluto and charon. The new proposal
1967: keywords are modp1024s160, modp2048s224 and modp2048s256. Thanks to Joy Latten
1968: from IBM for his contribution.
1969:
1970: - The IKEv1 pluto daemon supports RAM-based virtual IP pools using
1971: the rightsourceip directive with a subnet from which addresses
1972: are allocated.
1973:
1974: - The ipsec pki --gen and --pub commands now allow the output of
1975: private and public keys in PEM format using the --outform pem
1976: command line option.
1977:
1978: - The new DHCP plugin queries virtual IP addresses for clients from a DHCP
1979: server using broadcasts, or a defined server using the
1980: charon.plugins.dhcp.server strongswan.conf option. DNS/WINS server information
1981: is additionally served to clients if the DHCP server provides such
1982: information. The plugin is used in ipsec.conf configurations having
1983: rightsourceip set to %dhcp.
1984:
1985: - A new plugin called farp fakes ARP responses for virtual IP addresses
1986: handed out to clients from the IKEv2 daemon charon. The plugin lets a
1987: road-warrior act as a client on the local LAN if it uses a virtual IP
1988: from the responders subnet, e.g. acquired using the DHCP plugin.
1989:
1990: - The existing IKEv2 socket implementations have been migrated to the
1991: socket-default and the socket-raw plugins. The new socket-dynamic plugin
1992: binds sockets dynamically to ports configured via the left-/rightikeport
1993: ipsec.conf connection parameters.
1994:
1995: - The android charon plugin stores received DNS server information as "net.dns"
1996: system properties, as used by the Android platform.
1997:
1998:
1999: strongswan-4.3.6
2000: ----------------
2001:
2002: - The IKEv2 daemon supports RFC 3779 IP address block constraints
2003: carried as a critical X.509v3 extension in the peer certificate.
2004:
2005: - The ipsec pool --add|del dns|nbns command manages DNS and NBNS name
2006: server entries that are sent via the IKEv1 Mode Config or IKEv2
2007: Configuration Payload to remote clients.
2008:
2009: - The Camellia cipher can be used as an IKEv1 encryption algorithm.
2010:
2011: - The IKEv1 and IKEV2 daemons now check certificate path length constraints.
2012:
2013: - The new ipsec.conf conn option "inactivity" closes a CHILD_SA if no traffic
2014: was sent or received within the given interval. To close the complete IKE_SA
2015: if its only CHILD_SA was inactive, set the global strongswan.conf option
2016: "charon.inactivity_close_ike" to yes.
2017:
2018: - More detailed IKEv2 EAP payload information in debug output
2019:
2020: - IKEv2 EAP-SIM and EAP-AKA share joint libsimaka library
2021:
2022: - Added required userland changes for proper SHA256 and SHA384/512 in ESP that
2023: will be introduced with Linux 2.6.33. The "sha256"/"sha2_256" keyword now
2024: configures the kernel with 128 bit truncation, not the non-standard 96
2025: bit truncation used by previous releases. To use the old 96 bit truncation
2026: scheme, the new "sha256_96" proposal keyword has been introduced.
2027:
2028: - Fixed IPComp in tunnel mode, stripping out the duplicated outer header. This
2029: change makes IPcomp tunnel mode connections incompatible with previous
2030: releases; disable compression on such tunnels.
2031:
2032: - Fixed BEET mode connections on recent kernels by installing SAs with
2033: appropriate traffic selectors, based on a patch by Michael Rossberg.
2034:
2035: - Using extensions (such as BEET mode) and crypto algorithms (such as twofish,
2036: serpent, sha256_96) allocated in the private use space now require that we
2037: know its meaning, i.e. we are talking to strongSwan. Use the new
2038: "charon.send_vendor_id" option in strongswan.conf to let the remote peer know
2039: this is the case.
2040:
2041: - Experimental support for draft-eronen-ipsec-ikev2-eap-auth, where the
2042: responder omits public key authentication in favor of a mutual authentication
2043: method. To enable EAP-only authentication, set rightauth=eap on the responder
2044: to rely only on the MSK constructed AUTH payload. This not-yet standardized
2045: extension requires the strongSwan vendor ID introduced above.
2046:
2047: - The IKEv1 daemon ignores the Juniper SRX notification type 40001, thus
2048: allowing interoperability.
2049:
2050:
2051: strongswan-4.3.5
2052: ----------------
2053:
2054: - The IKEv1 pluto daemon can now use SQL-based address pools to deal out
2055: virtual IP addresses as a Mode Config server. The pool capability has been
2056: migrated from charon's sql plugin to a new attr-sql plugin which is loaded
2057: by libstrongswan and which can be used by both daemons either with a SQLite
2058: or MySQL database and the corresponding plugin.
2059:
2060: - Plugin names have been streamlined: EAP plugins now have a dash after eap
2061: (e.g. eap-sim), as it is used with the --enable-eap-sim ./configure option.
2062: Plugin configuration sections in strongswan.conf now use the same name as the
2063: plugin itself (i.e. with a dash). Make sure to update "load" directives and
2064: the affected plugin sections in existing strongswan.conf files.
2065:
2066: - The private/public key parsing and encoding has been split up into
2067: separate pkcs1, pgp, pem and dnskey plugins. The public key implementation
2068: plugins gmp, gcrypt and openssl can all make use of them.
2069:
2070: - The EAP-AKA plugin can use different backends for USIM/quintuplet
2071: calculations, very similar to the EAP-SIM plugin. The existing 3GPP2 software
2072: implementation has been migrated to a separate plugin.
2073:
2074: - The IKEv2 daemon charon gained basic PGP support. It can use locally installed
2075: peer certificates and can issue signatures based on RSA private keys.
2076:
2077: - The new 'ipsec pki' tool provides a set of commands to maintain a public
2078: key infrastructure. It currently supports operations to create RSA and ECDSA
2079: private/public keys, calculate fingerprints and issue or verify certificates.
2080:
2081: - Charon uses a monotonic time source for statistics and job queueing, behaving
2082: correctly if the system time changes (e.g. when using NTP).
2083:
2084: - In addition to time based rekeying, charon supports IPsec SA lifetimes based
2085: on processed volume or number of packets. They new ipsec.conf parameters
2086: 'lifetime' (an alias to 'keylife'), 'lifebytes' and 'lifepackets' handle
2087: SA timeouts, while the parameters 'margintime' (an alias to rekeymargin),
2088: 'marginbytes' and 'marginpackets' trigger the rekeying before a SA expires.
2089: The existing parameter 'rekeyfuzz' affects all margins.
2090:
2091: - If no CA/Gateway certificate is specified in the NetworkManager plugin,
2092: charon uses a set of trusted root certificates preinstalled by distributions.
2093: The directory containing CA certificates can be specified using the
2094: --with-nm-ca-dir=path configure option.
2095:
2096: - Fixed the encoding of the Email relative distinguished name in left|rightid
2097: statements.
2098:
2099: - Fixed the broken parsing of PKCS#7 wrapped certificates by the pluto daemon.
2100:
2101: - Fixed smartcard-based authentication in the pluto daemon which was broken by
2102: the ECDSA support introduced with the 4.3.2 release.
2103:
2104: - A patch contributed by Heiko Hund fixes mixed IPv6 in IPv4 and vice versa
2105: tunnels established with the IKEv1 pluto daemon.
2106:
2107: - The pluto daemon now uses the libstrongswan x509 plugin for certificates and
2108: CRls and the struct id type was replaced by identification_t used by charon
2109: and the libstrongswan library.
2110:
2111:
2112: strongswan-4.3.4
2113: ----------------
2114:
2115: - IKEv2 charon daemon ported to FreeBSD and Mac OS X. Installation details can
2116: be found on wiki.strongswan.org.
2117:
2118: - ipsec statusall shows the number of bytes transmitted and received over
2119: ESP connections configured by the IKEv2 charon daemon.
2120:
2121: - The IKEv2 charon daemon supports include files in ipsec.secrets.
2122:
2123:
2124: strongswan-4.3.3
2125: ----------------
2126:
2127: - The configuration option --enable-integrity-test plus the strongswan.conf
2128: option libstrongswan.integrity_test = yes activate integrity tests
2129: of the IKE daemons charon and pluto, libstrongswan and all loaded
2130: plugins. Thus dynamic library misconfigurations and non-malicious file
2131: manipulations can be reliably detected.
2132:
2133: - The new default setting libstrongswan.ecp_x_coordinate_only=yes allows
2134: IKEv1 interoperability with MS Windows using the ECP DH groups 19 and 20.
2135:
2136: - The IKEv1 pluto daemon now supports the AES-CCM and AES-GCM ESP
2137: authenticated encryption algorithms.
2138:
2139: - The IKEv1 pluto daemon now supports V4 OpenPGP keys.
2140:
2141: - The RDN parser vulnerability discovered by Orange Labs research team
2142: was not completely fixed in version 4.3.2. Some more modifications
2143: had to be applied to the asn1_length() function to make it robust.
2144:
2145:
2146: strongswan-4.3.2
2147: ----------------
2148:
2149: - The new gcrypt plugin provides symmetric cipher, hasher, RNG, Diffie-Hellman
2150: and RSA crypto primitives using the LGPL licensed GNU gcrypt library.
2151:
2152: - libstrongswan features an integrated crypto selftest framework for registered
2153: algorithms. The test-vector plugin provides a first set of test vectors and
2154: allows pluto and charon to rely on tested crypto algorithms.
2155:
2156: - pluto can now use all libstrongswan plugins with the exception of x509 and xcbc.
2157: Thanks to the openssl plugin, the ECP Diffie-Hellman groups 19, 20, 21, 25, and
2158: 26 as well as ECDSA-256, ECDSA-384, and ECDSA-521 authentication can be used
2159: with IKEv1.
2160:
2161: - Applying their fuzzing tool, the Orange Labs vulnerability research team found
2162: another two DoS vulnerabilities, one in the rather old ASN.1 parser of Relative
2163: Distinguished Names (RDNs) and a second one in the conversion of ASN.1 UTCTIME
2164: and GENERALIZEDTIME strings to a time_t value.
2165:
2166:
2167: strongswan-4.3.1
2168: ----------------
2169:
2170: - The nm plugin now passes DNS/NBNS server information to NetworkManager,
2171: allowing a gateway administrator to set DNS/NBNS configuration on clients
2172: dynamically.
2173:
2174: - The nm plugin also accepts CA certificates for gateway authentication. If
2175: a CA certificate is configured, strongSwan uses the entered gateway address
2176: as its identity, requiring the gateways certificate to contain the same as
2177: subjectAltName. This allows a gateway administrator to deploy the same
2178: certificates to Windows 7 and NetworkManager clients.
2179:
2180: - The command ipsec purgeike deletes IKEv2 SAs that don't have a CHILD SA.
2181: The command ipsec down <conn>{n} deletes CHILD SA instance n of connection
2182: <conn> whereas ipsec down <conn>{*} deletes all CHILD SA instances.
2183: The command ipsec down <conn>[n] deletes IKE SA instance n of connection
2184: <conn> plus dependent CHILD SAs whereas ipsec down <conn>[*] deletes all
2185: IKE SA instances of connection <conn>.
2186:
2187: - Fixed a regression introduced in 4.3.0 where EAP authentication calculated
2188: the AUTH payload incorrectly. Further, the EAP-MSCHAPv2 MSK key derivation
2189: has been updated to be compatible with the Windows 7 Release Candidate.
2190:
2191: - Refactored installation of triggering policies. Routed policies are handled
2192: outside of IKE_SAs to keep them installed in any case. A tunnel gets
2193: established only once, even if initiation is delayed due network outages.
2194:
2195: - Improved the handling of multiple acquire signals triggered by the kernel.
2196:
2197: - Fixed two DoS vulnerabilities in the charon daemon that were discovered by
2198: fuzzing techniques: 1) Sending a malformed IKE_SA_INIT request leaved an
2199: incomplete state which caused a null pointer dereference if a subsequent
2200: CREATE_CHILD_SA request was sent. 2) Sending an IKE_AUTH request with either
2201: a missing TSi or TSr payload caused a null pointer dereference because the
2202: checks for TSi and TSr were interchanged. The IKEv2 fuzzer used was
2203: developed by the Orange Labs vulnerability research team. The tool was
2204: initially written by Gabriel Campana and is now maintained by Laurent Butti.
2205:
2206: - Added support for AES counter mode in ESP in IKEv2 using the proposal
2207: keywords aes128ctr, aes192ctr and aes256ctr.
2208:
2209: - Further progress in refactoring pluto: Use of the curl and ldap plugins
2210: for fetching crls and OCSP. Use of the random plugin to get keying material
2211: from /dev/random or /dev/urandom. Use of the openssl plugin as an alternative
2212: to the aes, des, sha1, sha2, and md5 plugins. The blowfish, twofish, and
2213: serpent encryption plugins are now optional and are not enabled by default.
2214:
2215:
2216: strongswan-4.3.0
2217: ----------------
2218:
2219: - Support for the IKEv2 Multiple Authentication Exchanges extension (RFC4739).
2220: Initiators and responders can use several authentication rounds (e.g. RSA
2221: followed by EAP) to authenticate. The new ipsec.conf leftauth/rightauth and
2222: leftauth2/rightauth2 parameters define own authentication rounds or setup
2223: constraints for the remote peer. See the ipsec.conf man page for more details.
2224:
2225: - If glibc printf hooks (register_printf_function) are not available,
2226: strongSwan can use the vstr string library to run on non-glibc systems.
2227:
2228: - The IKEv2 charon daemon can now configure the ESP CAMELLIA-CBC cipher
2229: (esp=camellia128|192|256).
2230:
2231: - Refactored the pluto and scepclient code to use basic functions (memory
2232: allocation, leak detective, chunk handling, printf_hooks, strongswan.conf
2233: attributes, ASN.1 parser, etc.) from the libstrongswan library.
2234:
2235: - Up to two DNS and WINS servers to be sent via IKEv1 ModeConfig can be
2236: configured in the pluto section of strongswan.conf.
2237:
2238:
2239: strongswan-4.2.14
2240: -----------------
2241:
2242: - The new server-side EAP RADIUS plugin (--enable-eap-radius)
2243: relays EAP messages to and from a RADIUS server. Successfully
2244: tested with with a freeradius server using EAP-MD5 and EAP-SIM.
2245:
2246: - A vulnerability in the Dead Peer Detection (RFC 3706) code was found by
2247: Gerd v. Egidy <gerd.von.egidy@intra2net.com> of Intra2net AG affecting
2248: all Openswan and strongSwan releases. A malicious (or expired ISAKMP)
2249: R_U_THERE or R_U_THERE_ACK Dead Peer Detection packet can cause the
2250: pluto IKE daemon to crash and restart. No authentication or encryption
2251: is required to trigger this bug. One spoofed UDP packet can cause the
2252: pluto IKE daemon to restart and be unresponsive for a few seconds while
2253: restarting. This DPD null state vulnerability has been officially
2254: registered as CVE-2009-0790 and is fixed by this release.
2255:
2256: - ASN.1 to time_t conversion caused a time wrap-around for
2257: dates after Jan 18 03:14:07 UTC 2038 on 32-bit platforms.
2258: As a workaround such dates are set to the maximum representable
2259: time, i.e. Jan 19 03:14:07 UTC 2038.
2260:
2261: - Distinguished Names containing wildcards (*) are not sent in the
2262: IDr payload anymore.
2263:
2264:
2265: strongswan-4.2.13
2266: -----------------
2267:
2268: - Fixed a use-after-free bug in the DPD timeout section of the
2269: IKEv1 pluto daemon which sporadically caused a segfault.
2270:
2271: - Fixed a crash in the IKEv2 charon daemon occurring with
2272: mixed RAM-based and SQL-based virtual IP address pools.
2273:
2274: - Fixed ASN.1 parsing of algorithmIdentifier objects where the
2275: parameters field is optional.
2276:
2277: - Ported nm plugin to NetworkManager 7.1.
2278:
2279:
2280: strongswan-4.2.12
2281: -----------------
2282:
2283: - Support of the EAP-MSCHAPv2 protocol enabled by the option
2284: --enable-eap-mschapv2. Requires the MD4 hash algorithm enabled
2285: either by --enable-md4 or --enable-openssl.
2286:
2287: - Assignment of up to two DNS and up to two WINS servers to peers via
2288: the IKEv2 Configuration Payload (CP). The IPv4 or IPv6 nameserver
2289: addresses are defined in strongswan.conf.
2290:
2291: - The strongSwan applet for the Gnome NetworkManager is now built and
2292: distributed as a separate tarball under the name NetworkManager-strongswan.
2293:
2294:
2295: strongswan-4.2.11
2296: -----------------
2297:
2298: - Fixed ESP NULL encryption broken by the refactoring of keymat.c.
2299: Also introduced proper initialization and disposal of keying material.
2300:
2301: - Fixed the missing listing of connection definitions in ipsec statusall
2302: broken by an unfortunate local variable overload.
2303:
2304:
2305: strongswan-4.2.10
2306: -----------------
2307:
2308: - Several performance improvements to handle thousands of tunnels with almost
2309: linear upscaling. All relevant data structures have been replaced by faster
2310: counterparts with better lookup times.
2311:
2312: - Better parallelization to run charon on multiple cores. Due to improved
2313: resource locking and other optimizations the daemon can take full
2314: advantage of 16 or even more cores.
2315:
2316: - The load-tester plugin can use a NULL Diffie-Hellman group and simulate
2317: unique identities and certificates by signing peer certificates using a CA
2318: on the fly.
2319:
2320: - The redesigned stroke in-memory IP pool handles leases. The "ipsec leases"
2321: command queries assigned leases.
2322:
2323: - Added support for smartcards in charon by using the ENGINE API provided by
2324: OpenSSL, based on patches by Michael Roßberg.
2325:
2326: - The Padlock plugin supports the hardware RNG found on VIA CPUs to provide a
2327: reliable source of randomness.
2328:
2329: strongswan-4.2.9
2330: ----------------
2331:
2332: - Flexible configuration of logging subsystem allowing to log to multiple
2333: syslog facilities or to files using fine-grained log levels for each target.
2334:
2335: - Load testing plugin to do stress testing of the IKEv2 daemon against self
2336: or another host. Found and fixed issues during tests in the multi-threaded
2337: use of the OpenSSL plugin.
2338:
2339: - Added profiling code to synchronization primitives to find bottlenecks if
2340: running on multiple cores. Found and fixed an issue where parts of the
2341: Diffie-Hellman calculation acquired an exclusive lock. This greatly improves
2342: parallelization to multiple cores.
2343:
2344: - updown script invocation has been separated into a plugin of its own to
2345: further slim down the daemon core.
2346:
2347: - Separated IKE_SA/CHILD_SA key derivation process into a closed system,
2348: allowing future implementations to use a secured environment in e.g. kernel
2349: memory or hardware.
2350:
2351: - The kernel interface of charon has been modularized. XFRM NETLINK (default)
2352: and PFKEY (--enable-kernel-pfkey) interface plugins for the native IPsec
2353: stack of the Linux 2.6 kernel as well as a PFKEY interface for the KLIPS
2354: IPsec stack (--enable-kernel-klips) are provided.
2355:
2356: - Basic Mobile IPv6 support has been introduced, securing Binding Update
2357: messages as well as tunneled traffic between Mobile Node and Home Agent.
2358: The installpolicy=no option allows peaceful cooperation with a dominant
2359: mip6d daemon and the new type=transport_proxy implements the special MIPv6
2360: IPsec transport proxy mode where the IKEv2 daemon uses the Care-of-Address
2361: but the IPsec SA is set up for the Home Address.
2362:
2363: - Implemented migration of Mobile IPv6 connections using the KMADDRESS
2364: field contained in XFRM_MSG_MIGRATE messages sent by the mip6d daemon
2365: via the Linux 2.6.28 (or appropriately patched) kernel.
2366:
2367:
2368: strongswan-4.2.8
2369: ----------------
2370:
2371: - IKEv2 charon daemon supports authentication based on raw public keys
2372: stored in the SQL database backend. The ipsec listpubkeys command
2373: lists the available raw public keys via the stroke interface.
2374:
2375: - Several MOBIKE improvements: Detect changes in NAT mappings in DPD exchanges,
2376: handle events if kernel detects NAT mapping changes in UDP-encapsulated
2377: ESP packets (requires kernel patch), reuse old addresses in MOBIKE updates as
2378: long as possible and other fixes.
2379:
2380: - Fixed a bug in addr_in_subnet() which caused insertion of wrong source
2381: routes for destination subnets having netwmasks not being a multiple of 8 bits.
2382: Thanks go to Wolfgang Steudel, TU Ilmenau for reporting this bug.
2383:
2384:
2385: strongswan-4.2.7
2386: ----------------
2387:
2388: - Fixed a Denial-of-Service vulnerability where an IKE_SA_INIT message with
2389: a KE payload containing zeroes only can cause a crash of the IKEv2 charon
2390: daemon due to a NULL pointer returned by the mpz_export() function of the
2391: GNU Multiprecision Library (GMP). Thanks go to Mu Dynamics Research Labs
2392: for making us aware of this problem.
2393:
2394: - The new agent plugin provides a private key implementation on top of an
2395: ssh-agent.
2396:
2397: - The NetworkManager plugin has been extended to support certificate client
2398: authentication using RSA keys loaded from a file or using ssh-agent.
2399:
2400: - Daemon capability dropping has been ported to libcap and must be enabled
2401: explicitly --with-capabilities=libcap. Future version will support the
2402: newer libcap2 library.
2403:
2404: - ipsec listalgs lists the IKEv2 cryptografic algorithms registered with the
2405: charon keying daemon.
2406:
2407:
2408: strongswan-4.2.6
2409: ----------------
2410:
2411: - A NetworkManager plugin allows GUI-based configuration of road-warrior
2412: clients in a simple way. It features X509 based gateway authentication
2413: and EAP client authentication, tunnel setup/teardown and storing passwords
2414: in the Gnome Keyring.
2415:
2416: - A new EAP-GTC plugin implements draft-sheffer-ikev2-gtc-00.txt and allows
2417: username/password authentication against any PAM service on the gateway.
2418: The new EAP method interacts nicely with the NetworkManager plugin and allows
2419: client authentication against e.g. LDAP.
2420:
2421: - Improved support for the EAP-Identity method. The new ipsec.conf eap_identity
2422: parameter defines an additional identity to pass to the server in EAP
2423: authentication.
2424:
2425: - The "ipsec statusall" command now lists CA restrictions, EAP
2426: authentication types and EAP identities.
2427:
2428: - Fixed two multithreading deadlocks occurring when starting up
2429: several hundred tunnels concurrently.
2430:
2431: - Fixed the --enable-integrity-test configure option which
2432: computes a SHA-1 checksum over the libstrongswan library.
2433:
2434:
2435: strongswan-4.2.5
2436: ----------------
2437:
2438: - Consistent logging of IKE and CHILD SAs at the audit (AUD) level.
2439:
2440: - Improved the performance of the SQL-based virtual IP address pool
2441: by introducing an additional addresses table. The leases table
2442: storing only history information has become optional and can be
2443: disabled by setting charon.plugins.sql.lease_history = no in
2444: strongswan.conf.
2445:
2446: - The XFRM_STATE_AF_UNSPEC flag added to xfrm.h allows IPv4-over-IPv6
2447: and IPv6-over-IPv4 tunnels with the 2.6.26 and later Linux kernels.
2448:
2449: - management of different virtual IP pools for different
2450: network interfaces have become possible.
2451:
2452: - fixed a bug which prevented the assignment of more than 256
2453: virtual IP addresses from a pool managed by an sql database.
2454:
2455: - fixed a bug which did not delete own IPCOMP SAs in the kernel.
2456:
2457:
2458: strongswan-4.2.4
2459: ----------------
2460:
2461: - Added statistics functions to ipsec pool --status and ipsec pool --leases
2462: and input validation checks to various ipsec pool commands.
2463:
2464: - ipsec statusall now lists all loaded charon plugins and displays
2465: the negotiated IKEv2 cipher suite proposals.
2466:
2467: - The openssl plugin supports the elliptic curve Diffie-Hellman groups
2468: 19, 20, 21, 25, and 26.
2469:
2470: - The openssl plugin supports ECDSA authentication using elliptic curve
2471: X.509 certificates.
2472:
2473: - Fixed a bug in stroke which caused multiple charon threads to close
2474: the file descriptors during packet transfers over the stroke socket.
2475:
2476: - ESP sequence numbers are now migrated in IPsec SA updates handled by
2477: MOBIKE. Works only with Linux kernels >= 2.6.17.
2478:
2479:
2480: strongswan-4.2.3
2481: ----------------
2482:
2483: - Fixed the strongswan.conf path configuration problem that occurred when
2484: --sysconfig was not set explicitly in ./configure.
2485:
2486: - Fixed a number of minor bugs that where discovered during the 4th
2487: IKEv2 interoperability workshop in San Antonio, TX.
2488:
2489:
2490: strongswan-4.2.2
2491: ----------------
2492:
2493: - Plugins for libstrongswan and charon can optionally be loaded according
2494: to a configuration in strongswan.conf. Most components provide a
2495: "load = " option followed by a space separated list of plugins to load.
2496: This allows e.g. the fallback from a hardware crypto accelerator to
2497: to software-based crypto plugins.
2498:
2499: - Charons SQL plugin has been extended by a virtual IP address pool.
2500: Configurations with a rightsourceip=%poolname setting query a SQLite or
2501: MySQL database for leases. The "ipsec pool" command helps in administrating
2502: the pool database. See ipsec pool --help for the available options
2503:
2504: - The Authenticated Encryption Algorithms AES-CCM-8/12/16 and AES-GCM-8/12/16
2505: for ESP are now supported starting with the Linux 2.6.25 kernel. The
2506: syntax is e.g. esp=aes128ccm12 or esp=aes256gcm16.
2507:
2508:
2509: strongswan-4.2.1
2510: ----------------
2511:
2512: - Support for "Hash and URL" encoded certificate payloads has been implemented
2513: in the IKEv2 daemon charon. Using the "certuribase" option of a CA section
2514: allows to assign a base URL to all certificates issued by the specified CA.
2515: The final URL is then built by concatenating that base and the hex encoded
2516: SHA1 hash of the DER encoded certificate. Note that this feature is disabled
2517: by default and must be enabled using the option "charon.hash_and_url".
2518:
2519: - The IKEv2 daemon charon now supports the "uniqueids" option to close multiple
2520: IKE_SAs with the same peer. The option value "keep" prefers existing
2521: connection setups over new ones, where the value "replace" replaces existing
2522: connections.
2523:
2524: - The crypto factory in libstrongswan additionally supports random number
2525: generators, plugins may provide other sources of randomness. The default
2526: plugin reads raw random data from /dev/(u)random.
2527:
2528: - Extended the credential framework by a caching option to allow plugins
2529: persistent caching of fetched credentials. The "cachecrl" option has been
2530: re-implemented.
2531:
2532: - The new trustchain verification introduced in 4.2.0 has been parallelized.
2533: Threads fetching CRL or OCSP information no longer block other threads.
2534:
2535: - A new IKEv2 configuration attribute framework has been introduced allowing
2536: plugins to provide virtual IP addresses, and in the future, other
2537: configuration attribute services (e.g. DNS/WINS servers).
2538:
2539: - The stroke plugin has been extended to provide virtual IP addresses from
2540: a pool defined in ipsec.conf. The "rightsourceip" parameter now accepts
2541: address pools in CIDR notation (e.g. 10.1.1.0/24). The parameter also accepts
2542: the value "%poolname", where "poolname" identifies a pool provided by a
2543: separate plugin.
2544:
2545: - Fixed compilation on uClibc and a couple of other minor bugs.
2546:
2547: - Set DPD defaults in ipsec starter to dpd_delay=30s and dpd_timeout=150s.
2548:
2549: - The IKEv1 pluto daemon now supports the ESP encryption algorithm CAMELLIA
2550: with key lengths of 128, 192, and 256 bits, as well as the authentication
2551: algorithm AES_XCBC_MAC. Configuration example: esp=camellia192-aesxcbc.
2552:
2553:
2554: strongswan-4.2.0
2555: ----------------
2556:
2557: - libstrongswan has been modularized to attach crypto algorithms,
2558: credential implementations (keys, certificates) and fetchers dynamically
2559: through plugins. Existing code has been ported to plugins:
2560: - RSA/Diffie-Hellman implementation using the GNU Multi Precision library
2561: - X509 certificate system supporting CRLs, OCSP and attribute certificates
2562: - Multiple plugins providing crypto algorithms in software
2563: - CURL and OpenLDAP fetcher
2564:
2565: - libstrongswan gained a relational database API which uses pluggable database
2566: providers. Plugins for MySQL and SQLite are available.
2567:
2568: - The IKEv2 keying daemon charon is more extensible. Generic plugins may provide
2569: connection configuration, credentials and EAP methods or control the daemon.
2570: Existing code has been ported to plugins:
2571: - EAP-AKA, EAP-SIM, EAP-MD5 and EAP-Identity
2572: - stroke configuration, credential and control (compatible to pluto)
2573: - XML bases management protocol to control and query the daemon
2574: The following new plugins are available:
2575: - An experimental SQL configuration, credential and logging plugin on
2576: top of either MySQL or SQLite
2577: - A unit testing plugin to run tests at daemon startup
2578:
2579: - The authentication and credential framework in charon has been heavily
2580: refactored to support modular credential providers, proper
2581: CERTREQ/CERT payload exchanges and extensible authorization rules.
2582:
2583: - The framework of strongSwan Manager has evolved to the web application
2584: framework libfast (FastCGI Application Server w/ Templates) and is usable
2585: by other applications.
2586:
2587:
2588: strongswan-4.1.11
2589: -----------------
2590:
2591: - IKE rekeying in NAT situations did not inherit the NAT conditions
2592: to the rekeyed IKE_SA so that the UDP encapsulation was lost with
2593: the next CHILD_SA rekeying.
2594:
2595: - Wrong type definition of the next_payload variable in id_payload.c
2596: caused an INVALID_SYNTAX error on PowerPC platforms.
2597:
2598: - Implemented IKEv2 EAP-SIM server and client test modules that use
2599: triplets stored in a file. For details on the configuration see
2600: the scenario 'ikev2/rw-eap-sim-rsa'.
2601:
2602:
2603: strongswan-4.1.10
2604: -----------------
2605:
2606: - Fixed error in the ordering of the certinfo_t records in the ocsp cache that
2607: caused multiple entries of the same serial number to be created.
2608:
2609: - Implementation of a simple EAP-MD5 module which provides CHAP
2610: authentication. This may be interesting in conjunction with certificate
2611: based server authentication, as weak passwords can't be brute forced
2612: (in contradiction to traditional IKEv2 PSK).
2613:
2614: - A complete software based implementation of EAP-AKA, using algorithms
2615: specified in 3GPP2 (S.S0055). This implementation does not use an USIM,
2616: but reads the secrets from ipsec.secrets. Make sure to read eap_aka.h
2617: before using it.
2618:
2619: - Support for vendor specific EAP methods using Expanded EAP types. The
2620: interface to EAP modules has been slightly changed, so make sure to
2621: check the changes if you're already rolling your own modules.
2622:
2623:
2624: strongswan-4.1.9
2625: ----------------
2626:
2627: - The default _updown script now dynamically inserts and removes ip6tables
2628: firewall rules if leftfirewall=yes is set in IPv6 connections. New IPv6
2629: net-net and roadwarrior (PSK/RSA) scenarios for both IKEv1 and IKEV2 were
2630: added.
2631:
2632: - Implemented RFC4478 repeated authentication to force EAP/Virtual-IP clients
2633: to reestablish an IKE_SA within a given timeframe.
2634:
2635: - strongSwan Manager supports configuration listing, initiation and termination
2636: of IKE and CHILD_SAs.
2637:
2638: - Fixes and improvements to multithreading code.
2639:
2640: - IKEv2 plugins have been renamed to libcharon-* to avoid naming conflicts.
2641: Make sure to remove the old plugins in $libexecdir/ipsec, otherwise they get
2642: loaded twice.
2643:
2644:
2645: strongswan-4.1.8
2646: ----------------
2647:
2648: - Removed recursive pthread mutexes since uClibc doesn't support them.
2649:
2650:
2651: strongswan-4.1.7
2652: ----------------
2653:
2654: - In NAT traversal situations and multiple queued Quick Modes,
2655: those pending connections inserted by auto=start after the
2656: port floating from 500 to 4500 were erroneously deleted.
2657:
2658: - Added a "forceencaps" connection parameter to enforce UDP encapsulation
2659: to surmount restrictive firewalls. NAT detection payloads are faked to
2660: simulate a NAT situation and trick the other peer into NAT mode (IKEv2 only).
2661:
2662: - Preview of strongSwan Manager, a web based configuration and monitoring
2663: application. It uses a new XML control interface to query the IKEv2 daemon
2664: (see https://wiki.strongswan.org/wiki/Manager).
2665:
2666: - Experimental SQLite configuration backend which will provide the configuration
2667: interface for strongSwan Manager in future releases.
2668:
2669: - Further improvements to MOBIKE support.
2670:
2671:
2672: strongswan-4.1.6
2673: ----------------
2674:
2675: - Since some third party IKEv2 implementations run into
2676: problems with strongSwan announcing MOBIKE capability per
2677: default, MOBIKE can be disabled on a per-connection-basis
2678: using the mobike=no option. Whereas mobike=no disables the
2679: sending of the MOBIKE_SUPPORTED notification and the floating
2680: to UDP port 4500 with the IKE_AUTH request even if no NAT
2681: situation has been detected, strongSwan will still support
2682: MOBIKE acting as a responder.
2683:
2684: - the default ipsec routing table plus its corresponding priority
2685: used for inserting source routes has been changed from 100 to 220.
2686: It can be configured using the --with-ipsec-routing-table and
2687: --with-ipsec-routing-table-prio options.
2688:
2689: - the --enable-integrity-test configure option tests the
2690: integrity of the libstrongswan crypto code during the charon
2691: startup.
2692:
2693: - the --disable-xauth-vid configure option disables the sending
2694: of the XAUTH vendor ID. This can be used as a workaround when
2695: interoperating with some Windows VPN clients that get into
2696: trouble upon reception of an XAUTH VID without eXtended
2697: AUTHentication having been configured.
2698:
2699: - ipsec stroke now supports the rereadsecrets, rereadaacerts,
2700: rereadacerts, and listacerts options.
2701:
2702:
2703: strongswan-4.1.5
2704: ----------------
2705:
2706: - If a DNS lookup failure occurs when resolving right=%<FQDN>
2707: or right=<FQDN> combined with rightallowany=yes then the
2708: connection is not updated by ipsec starter thus preventing
2709: the disruption of an active IPsec connection. Only if the DNS
2710: lookup successfully returns with a changed IP address the
2711: corresponding connection definition is updated.
2712:
2713: - Routes installed by the keying daemons are now in a separate
2714: routing table with the ID 100 to avoid conflicts with the main
2715: table. Route lookup for IKEv2 traffic is done in userspace to ignore
2716: routes installed for IPsec, as IKE traffic shouldn't get encapsulated.
2717:
2718:
2719: strongswan-4.1.4
2720: ----------------
2721:
2722: - The pluto IKEv1 daemon now exhibits the same behaviour as its
2723: IKEv2 companion charon by inserting an explicit route via the
2724: _updown script only if a sourceip exists. This is admissible
2725: since routing through the IPsec tunnel is handled automatically
2726: by NETKEY's IPsec policies. As a consequence the left|rightnexthop
2727: parameter is not required any more.
2728:
2729: - The new IKEv1 parameter right|leftallowany parameters helps to handle
2730: the case where both peers possess dynamic IP addresses that are
2731: usually resolved using DynDNS or a similar service. The configuration
2732:
2733: right=peer.foo.bar
2734: rightallowany=yes
2735:
2736: can be used by the initiator to start up a connection to a peer
2737: by resolving peer.foo.bar into the currently allocated IP address.
2738: Thanks to the rightallowany flag the connection behaves later on
2739: as
2740:
2741: right=%any
2742:
2743: so that the peer can rekey the connection as an initiator when his
2744: IP address changes. An alternative notation is
2745:
2746: right=%peer.foo.bar
2747:
2748: which will implicitly set rightallowany=yes.
2749:
2750: - ipsec starter now fails more gracefully in the presence of parsing
2751: errors. Flawed ca and conn section are discarded and pluto is started
2752: if non-fatal errors only were encountered. If right=%peer.foo.bar
2753: cannot be resolved by DNS then right=%any will be used so that passive
2754: connections as a responder are still possible.
2755:
2756: - The new pkcs11initargs parameter that can be placed in the
2757: setup config section of /etc/ipsec.conf allows the definition
2758: of an argument string that is used with the PKCS#11 C_Initialize()
2759: function. This non-standard feature is required by the NSS softoken
2760: library. This patch was contributed by Robert Varga.
2761:
2762: - Fixed a bug in ipsec starter introduced by strongswan-2.8.5
2763: which caused a segmentation fault in the presence of unknown
2764: or misspelt keywords in ipsec.conf. This bug fix was contributed
2765: by Robert Varga.
2766:
2767: - Partial support for MOBIKE in IKEv2. The initiator acts on interface/
2768: address configuration changes and updates IKE and IPsec SAs dynamically.
2769:
2770:
2771: strongswan-4.1.3
2772: ----------------
2773:
2774: - IKEv2 peer configuration selection now can be based on a given
2775: certification authority using the rightca= statement.
2776:
2777: - IKEv2 authentication based on RSA signatures now can handle multiple
2778: certificates issued for a given peer ID. This allows a smooth transition
2779: in the case of a peer certificate renewal.
2780:
2781: - IKEv2: Support for requesting a specific virtual IP using leftsourceip on the
2782: client and returning requested virtual IPs using rightsourceip=%config
2783: on the server. If the server does not support configuration payloads, the
2784: client enforces its leftsourceip parameter.
2785:
2786: - The ./configure options --with-uid/--with-gid allow pluto and charon
2787: to drop their privileges to a minimum and change to an other UID/GID. This
2788: improves the systems security, as a possible intruder may only get the
2789: CAP_NET_ADMIN capability.
2790:
2791: - Further modularization of charon: Pluggable control interface and
2792: configuration backend modules provide extensibility. The control interface
2793: for stroke is included, and further interfaces using DBUS (NetworkManager)
2794: or XML are on the way. A backend for storing configurations in the daemon
2795: is provided and more advanced backends (using e.g. a database) are trivial
2796: to implement.
2797:
2798: - Fixed a compilation failure in libfreeswan occurring with Linux kernel
2799: headers > 2.6.17.
2800:
2801:
2802: strongswan-4.1.2
2803: ----------------
2804:
2805: - Support for an additional Diffie-Hellman exchange when creating/rekeying
2806: a CHILD_SA in IKEv2 (PFS). PFS is enabled when the proposal contains a
2807: DH group (e.g. "esp=aes128-sha1-modp1536"). Further, DH group negotiation
2808: is implemented properly for rekeying.
2809:
2810: - Support for the AES-XCBC-96 MAC algorithm for IPsec SAs when using IKEv2
2811: (requires linux >= 2.6.20). It is enabled using e.g. "esp=aes256-aesxcbc".
2812:
2813: - Working IPv4-in-IPv6 and IPv6-in-IPv4 tunnels for linux >= 2.6.21.
2814:
2815: - Added support for EAP modules which do not establish an MSK.
2816:
2817: - Removed the dependencies from the /usr/include/linux/ headers by
2818: including xfrm.h, ipsec.h, and pfkeyv2.h in the distribution.
2819:
2820: - crlNumber is now listed by ipsec listcrls
2821:
2822: - The xauth_modules.verify_secret() function now passes the
2823: connection name.
2824:
2825:
2826: strongswan-4.1.1
2827: ----------------
2828:
2829: - Server side cookie support. If to may IKE_SAs are in CONNECTING state,
2830: cookies are enabled and protect against DoS attacks with faked source
2831: addresses. Number of IKE_SAs in CONNECTING state is also limited per
2832: peer address to avoid resource exhaustion. IKE_SA_INIT messages are
2833: compared to properly detect retransmissions and incoming retransmits are
2834: detected even if the IKE_SA is blocked (e.g. doing OCSP fetches).
2835:
2836: - The IKEv2 daemon charon now supports dynamic http- and ldap-based CRL
2837: fetching enabled by crlcheckinterval > 0 and caching fetched CRLs
2838: enabled by cachecrls=yes.
2839:
2840: - Added the configuration options --enable-nat-transport which enables
2841: the potentially insecure NAT traversal for IPsec transport mode and
2842: --disable-vendor-id which disables the sending of the strongSwan
2843: vendor ID.
2844:
2845: - Fixed a long-standing bug in the pluto IKEv1 daemon which caused
2846: a segmentation fault if a malformed payload was detected in the
2847: IKE MR2 message and pluto tried to send an encrypted notification
2848: message.
2849:
2850: - Added the NATT_IETF_02_N Vendor ID in order to support IKEv1 connections
2851: with Windows 2003 Server which uses a wrong VID hash.
2852:
2853:
2854: strongswan-4.1.0
2855: ----------------
2856:
2857: - Support of SHA2_384 hash function for protecting IKEv1
2858: negotiations and support of SHA2 signatures in X.509 certificates.
2859:
2860: - Fixed a serious bug in the computation of the SHA2-512 HMAC
2861: function. Introduced automatic self-test of all IKEv1 hash
2862: and hmac functions during pluto startup. Failure of a self-test
2863: currently issues a warning only but does not exit pluto [yet].
2864:
2865: - Support for SHA2-256/384/512 PRF and HMAC functions in IKEv2.
2866:
2867: - Full support of CA information sections. ipsec listcainfos
2868: now shows all collected crlDistributionPoints and OCSP
2869: accessLocations.
2870:
2871: - Support of the Online Certificate Status Protocol (OCSP) for IKEv2.
2872: This feature requires the HTTP fetching capabilities of the libcurl
2873: library which must be enabled by setting the --enable-http configure
2874: option.
2875:
2876: - Refactored core of the IKEv2 message processing code, allowing better
2877: code reuse and separation.
2878:
2879: - Virtual IP support in IKEv2 using INTERNAL_IP4/6_ADDRESS configuration
2880: payload. Additionally, the INTERNAL_IP4/6_DNS attribute is interpreted
2881: by the requestor and installed in a resolv.conf file.
2882:
2883: - The IKEv2 daemon charon installs a route for each IPsec policy to use
2884: the correct source address even if an application does not explicitly
2885: specify it.
2886:
2887: - Integrated the EAP framework into charon which loads pluggable EAP library
2888: modules. The ipsec.conf parameter authby=eap initiates EAP authentication
2889: on the client side, while the "eap" parameter on the server side defines
2890: the EAP method to use for client authentication.
2891: A generic client side EAP-Identity module and an EAP-SIM authentication
2892: module using a third party card reader implementation are included.
2893:
2894: - Added client side support for cookies.
2895:
2896: - Integrated the fixes done at the IKEv2 interoperability bakeoff, including
2897: strict payload order, correct INVALID_KE_PAYLOAD rejection and other minor
2898: fixes to enhance interoperability with other implementations.
2899:
2900:
2901: strongswan-4.0.7
2902: ----------------
2903:
2904: - strongSwan now interoperates with the NCP Secure Entry Client,
2905: the Shrew Soft VPN Client, and the Cisco VPN client, doing both
2906: XAUTH and Mode Config.
2907:
2908: - UNITY attributes are now recognized and UNITY_BANNER is set
2909: to a default string.
2910:
2911:
2912: strongswan-4.0.6
2913: ----------------
2914:
2915: - IKEv1: Support for extended authentication (XAUTH) in combination
2916: with ISAKMP Main Mode RSA or PSK authentication. Both client and
2917: server side were implemented. Handling of user credentials can
2918: be done by a run-time loadable XAUTH module. By default user
2919: credentials are stored in ipsec.secrets.
2920:
2921: - IKEv2: Support for reauthentication when rekeying
2922:
2923: - IKEv2: Support for transport mode
2924:
2925: - fixed a lot of bugs related to byte order
2926:
2927: - various other bugfixes
2928:
2929:
2930: strongswan-4.0.5
2931: ----------------
2932:
2933: - IKEv1: Implementation of ModeConfig push mode via the new connection
2934: keyword modeconfig=push allows interoperability with Cisco VPN gateways.
2935:
2936: - IKEv1: The command ipsec statusall now shows "DPD active" for all
2937: ISAKMP SAs that are under active Dead Peer Detection control.
2938:
2939: - IKEv2: Charon's logging and debugging framework has been completely rewritten.
2940: Instead of logger, special printf() functions are used to directly
2941: print objects like hosts (%H) identifications (%D), certificates (%Q),
2942: etc. The number of debugging levels have been reduced to:
2943:
2944: 0 (audit), 1 (control), 2 (controlmore), 3 (raw), 4 (private)
2945:
2946: The debugging levels can either be specified statically in ipsec.conf as
2947:
2948: config setup
2949: charondebug="lib 1, cfg 3, net 2"
2950:
2951: or changed at runtime via stroke as
2952:
2953: ipsec stroke loglevel cfg 2
2954:
2955:
2956: strongswan-4.0.4
2957: ----------------
2958:
2959: - Implemented full support for IPv6-in-IPv6 tunnels.
2960:
2961: - Added configuration options for dead peer detection in IKEv2. dpd_action
2962: types "clear", "hold" and "restart" are supported. The dpd_timeout
2963: value is not used, as the normal retransmission policy applies to
2964: detect dead peers. The dpd_delay parameter enables sending of empty
2965: informational message to detect dead peers in case of inactivity.
2966:
2967: - Added support for preshared keys in IKEv2. PSK keys configured in
2968: ipsec.secrets are loaded. The authby parameter specifies the authentication
2969: method to authenticate ourself, the other peer may use PSK or RSA.
2970:
2971: - Changed retransmission policy to respect the keyingtries parameter.
2972:
2973: - Added private key decryption. PEM keys encrypted with AES-128/192/256
2974: or 3DES are supported.
2975:
2976: - Implemented DES/3DES algorithms in libstrongswan. 3DES can be used to
2977: encrypt IKE traffic.
2978:
2979: - Implemented SHA-256/384/512 in libstrongswan, allows usage of certificates
2980: signed with such a hash algorithm.
2981:
2982: - Added initial support for updown scripts. The actions up-host/client and
2983: down-host/client are executed. The leftfirewall=yes parameter
2984: uses the default updown script to insert dynamic firewall rules, a custom
2985: updown script may be specified with the leftupdown parameter.
2986:
2987:
2988: strongswan-4.0.3
2989: ----------------
2990:
2991: - Added support for the auto=route ipsec.conf parameter and the
2992: ipsec route/unroute commands for IKEv2. This allows to set up IKE_SAs and
2993: CHILD_SAs dynamically on demand when traffic is detected by the
2994: kernel.
2995:
2996: - Added support for rekeying IKE_SAs in IKEv2 using the ikelifetime parameter.
2997: As specified in IKEv2, no reauthentication is done (unlike in IKEv1), only
2998: new keys are generated using perfect forward secrecy. An optional flag
2999: which enforces reauthentication will be implemented later.
3000:
3001: - "sha" and "sha1" are now treated as synonyms in the ike= and esp=
3002: algorithm configuration statements.
3003:
3004:
3005: strongswan-4.0.2
3006: ----------------
3007:
3008: - Full X.509 certificate trust chain verification has been implemented.
3009: End entity certificates can be exchanged via CERT payloads. The current
3010: default is leftsendcert=always, since CERTREQ payloads are not supported
3011: yet. Optional CRLs must be imported locally into /etc/ipsec.d/crls.
3012:
3013: - Added support for leftprotoport/rightprotoport parameters in IKEv2. IKEv2
3014: would offer more possibilities for traffic selection, but the Linux kernel
3015: currently does not support it. That's why we stick with these simple
3016: ipsec.conf rules for now.
3017:
3018: - Added Dead Peer Detection (DPD) which checks liveliness of remote peer if no
3019: IKE or ESP traffic is received. DPD is currently hardcoded (dpdaction=clear,
3020: dpddelay=60s).
3021:
3022: - Initial NAT traversal support in IKEv2. Charon includes NAT detection
3023: notify payloads to detect NAT routers between the peers. It switches
3024: to port 4500, uses UDP encapsulated ESP packets, handles peer address
3025: changes gracefully and sends keep alive message periodically.
3026:
3027: - Reimplemented IKE_SA state machine for charon, which allows simultaneous
3028: rekeying, more shared code, cleaner design, proper retransmission
3029: and a more extensible code base.
3030:
3031: - The mixed PSK/RSA roadwarrior detection capability introduced by the
3032: strongswan-2.7.0 release necessitated the pre-parsing of the IKE proposal
3033: payloads by the responder right before any defined IKE Main Mode state had
3034: been established. Although any form of bad proposal syntax was being correctly
3035: detected by the payload parser, the subsequent error handler didn't check
3036: the state pointer before logging current state information, causing an
3037: immediate crash of the pluto keying daemon due to a NULL pointer.
3038:
3039:
3040: strongswan-4.0.1
3041: ----------------
3042:
3043: - Added algorithm selection to charon: New default algorithms for
3044: ike=aes128-sha-modp2048, as both daemons support it. The default
3045: for IPsec SAs is now esp=aes128-sha,3des-md5. charon handles
3046: the ike/esp parameter the same way as pluto. As this syntax does
3047: not allow specification of a pseudo random function, the same
3048: algorithm as for integrity is used (currently sha/md5). Supported
3049: algorithms for IKE:
3050: Encryption: aes128, aes192, aes256
3051: Integrity/PRF: md5, sha (using hmac)
3052: DH-Groups: modp768, 1024, 1536, 2048, 4096, 8192
3053: and for ESP:
3054: Encryption: aes128, aes192, aes256, 3des, blowfish128,
3055: blowfish192, blowfish256
3056: Integrity: md5, sha1
3057: More IKE encryption algorithms will come after porting libcrypto into
3058: libstrongswan.
3059:
3060: - initial support for rekeying CHILD_SAs using IKEv2. Currently no
3061: perfect forward secrecy is used. The rekeying parameters rekey,
3062: rekeymargin, rekeyfuzz and keylife from ipsec.conf are now supported
3063: when using IKEv2. WARNING: charon currently is unable to handle
3064: simultaneous rekeying. To avoid such a situation, use a large
3065: rekeyfuzz, or even better, set rekey=no on one peer.
3066:
3067: - support for host2host, net2net, host2net (roadwarrior) tunnels
3068: using predefined RSA certificates (see uml scenarios for
3069: configuration examples).
3070:
3071: - new build environment featuring autotools. Features such
3072: as HTTP, LDAP and smartcard support may be enabled using
3073: the ./configure script. Changing install directories
3074: is possible, too. See ./configure --help for more details.
3075:
3076: - better integration of charon with ipsec starter, which allows
3077: (almost) transparent operation with both daemons. charon
3078: handles ipsec commands up, down, status, statusall, listall,
3079: listcerts and allows proper load, reload and delete of connections
3080: via ipsec starter.
3081:
3082:
3083: strongswan-4.0.0
3084: ----------------
3085:
3086: - initial support of the IKEv2 protocol. Connections in
3087: ipsec.conf designated by keyexchange=ikev2 are negotiated
3088: by the new IKEv2 charon keying daemon whereas those marked
3089: by keyexchange=ikev1 or the default keyexchange=ike are
3090: handled thy the IKEv1 pluto keying daemon. Currently only
3091: a limited subset of functions are available with IKEv2
3092: (Default AES encryption, authentication based on locally
3093: imported X.509 certificates, unencrypted private RSA keys
3094: in PKCS#1 file format, limited functionality of the ipsec
3095: status command).
3096:
3097:
3098: strongswan-2.7.0
3099: ----------------
3100:
3101: - the dynamic iptables rules from the _updown_x509 template
3102: for KLIPS and the _updown_policy template for NETKEY have
3103: been merged into the default _updown script. The existing
3104: left|rightfirewall keyword causes the automatic insertion
3105: and deletion of ACCEPT rules for tunneled traffic upon
3106: the successful setup and teardown of an IPsec SA, respectively.
3107: left|rightfirewall can be used with KLIPS under any Linux 2.4
3108: kernel or with NETKEY under a Linux kernel version >= 2.6.16
3109: in conjunction with iptables >= 1.3.5. For NETKEY under a Linux
3110: kernel version < 2.6.16 which does not support IPsec policy
3111: matching yet, please continue to use a copy of the _updown_espmark
3112: template loaded via the left|rightupdown keyword.
3113:
3114: - a new left|righthostaccess keyword has been introduced which
3115: can be used in conjunction with left|rightfirewall and the
3116: default _updown script. By default leftfirewall=yes inserts
3117: a bi-directional iptables FORWARD rule for a local client network
3118: with a netmask different from 255.255.255.255 (single host).
3119: This does not allow to access the VPN gateway host via its
3120: internal network interface which is part of the client subnet
3121: because an iptables INPUT and OUTPUT rule would be required.
3122: lefthostaccess=yes will cause this additional ACCEPT rules to
3123: be inserted.
3124:
3125: - mixed PSK|RSA roadwarriors are now supported. The ISAKMP proposal
3126: payload is preparsed in order to find out whether the roadwarrior
3127: requests PSK or RSA so that a matching connection candidate can
3128: be found.
3129:
3130:
3131: strongswan-2.6.4
3132: ----------------
3133:
3134: - the new _updown_policy template allows ipsec policy based
3135: iptables firewall rules. Required are iptables version
3136: >= 1.3.5 and linux kernel >= 2.6.16. This script obsoletes
3137: the _updown_espmark template, so that no INPUT mangle rules
3138: are required any more.
3139:
3140: - added support of DPD restart mode
3141:
3142: - ipsec starter now allows the use of wildcards in include
3143: statements as e.g. in "include /etc/my_ipsec/*.conf".
3144: Patch courtesy of Matthias Haas.
3145:
3146: - the Netscape OID 'employeeNumber' is now recognized and can be
3147: used as a Relative Distinguished Name in certificates.
3148:
3149:
3150: strongswan-2.6.3
3151: ----------------
3152:
3153: - /etc/init.d/ipsec or /etc/rc.d/ipsec is now a copy of the ipsec
3154: command and not of ipsec setup any more.
3155:
3156: - ipsec starter now supports AH authentication in conjunction with
3157: ESP encryption. AH authentication is configured in ipsec.conf
3158: via the auth=ah parameter.
3159:
3160: - The command ipsec scencrypt|scdecrypt <args> is now an alias for
3161: ipsec whack --scencrypt|scdecrypt <args>.
3162:
3163: - get_sa_info() now determines for the native netkey IPsec stack
3164: the exact time of the last use of an active eroute. This information
3165: is used by the Dead Peer Detection algorithm and is also displayed by
3166: the ipsec status command.
3167:
3168:
3169: strongswan-2.6.2
3170: ----------------
3171:
3172: - running under the native Linux 2.6 IPsec stack, the function
3173: get_sa_info() is called by ipsec auto --status to display the current
3174: number of transmitted bytes per IPsec SA.
3175:
3176: - get_sa_info() is also used by the Dead Peer Detection process to detect
3177: recent ESP activity. If ESP traffic was received from the peer within
3178: the last dpd_delay interval then no R_Y_THERE notification must be sent.
3179:
3180: - strongSwan now supports the Relative Distinguished Name "unstructuredName"
3181: in ID_DER_ASN1_DN identities. The following notations are possible:
3182:
3183: rightid="unstructuredName=John Doe"
3184: rightid="UN=John Doe"
3185:
3186: - fixed a long-standing bug which caused PSK-based roadwarrior connections
3187: to segfault in the function id.c:same_id() called by keys.c:get_secret()
3188: if an FQDN, USER_FQDN, or Key ID was defined, as in the following example.
3189:
3190: conn rw
3191: right=%any
3192: rightid=@foo.bar
3193: authby=secret
3194:
3195: - the ipsec command now supports most ipsec auto commands (e.g. ipsec listall).
3196:
3197: - ipsec starter didn't set host_addr and client.addr ports in whack msg.
3198:
3199: - in order to guarantee backwards-compatibility with the script-based
3200: auto function (e.g. auto --replace), the ipsec starter scripts stores
3201: the defaultroute information in the temporary file /var/run/ipsec.info.
3202:
3203: - The compile-time option USE_XAUTH_VID enables the sending of the XAUTH
3204: Vendor ID which is expected by Cisco PIX 7 boxes that act as IKE Mode Config
3205: servers.
3206:
3207: - the ipsec starter now also recognizes the parameters authby=never and
3208: type=passthrough|pass|drop|reject.
3209:
3210:
3211: strongswan-2.6.1
3212: ----------------
3213:
3214: - ipsec starter now supports the also parameter which allows
3215: a modular structure of the connection definitions. Thus
3216: "ipsec start" is now ready to replace "ipsec setup".
3217:
3218:
3219: strongswan-2.6.0
3220: ----------------
3221:
3222: - Mathieu Lafon's popular ipsec starter tool has been added to the
3223: strongSwan distribution. Many thanks go to Stephan Scholz from astaro
3224: for his integration work. ipsec starter is a C program which is going
3225: to replace the various shell and awk starter scripts (setup, _plutoload,
3226: _plutostart, _realsetup, _startklips, _confread, and auto). Since
3227: ipsec.conf is now parsed only once, the starting of multiple tunnels is
3228: accelerated tremendously.
3229:
3230: - Added support of %defaultroute to the ipsec starter. If the IP address
3231: changes, a HUP signal to the ipsec starter will automatically
3232: reload pluto's connections.
3233:
3234: - moved most compile time configurations from pluto/Makefile to
3235: Makefile.inc by defining the options USE_LIBCURL, USE_LDAP,
3236: USE_SMARTCARD, and USE_NAT_TRAVERSAL_TRANSPORT_MODE.
3237:
3238: - removed the ipsec verify and ipsec newhostkey commands
3239:
3240: - fixed some 64-bit issues in formatted print statements
3241:
3242: - The scepclient functionality implementing the Simple Certificate
3243: Enrollment Protocol (SCEP) is nearly complete but hasn't been
3244: documented yet.
3245:
3246:
3247: strongswan-2.5.7
3248: ----------------
3249:
3250: - CA certificates are now automatically loaded from a smartcard
3251: or USB crypto token and appear in the ipsec auto --listcacerts
3252: listing.
3253:
3254:
3255: strongswan-2.5.6
3256: ----------------
3257:
3258: - when using "ipsec whack --scencrypt <data>" with a PKCS#11
3259: library that does not support the C_Encrypt() Cryptoki
3260: function (e.g. OpenSC), the RSA encryption is done in
3261: software using the public key fetched from the smartcard.
3262:
3263: - The scepclient function now allows to define the
3264: validity of a self-signed certificate using the --days,
3265: --startdate, and --enddate options. The default validity
3266: has been changed from one year to five years.
3267:
3268:
3269: strongswan-2.5.5
3270: ----------------
3271:
3272: - the config setup parameter pkcs11proxy=yes opens pluto's PKCS#11
3273: interface to other applications for RSA encryption and decryption
3274: via the whack interface. Notation:
3275:
3276: ipsec whack --scencrypt <data>
3277: [--inbase 16|hex|64|base64|256|text|ascii]
3278: [--outbase 16|hex|64|base64|256|text|ascii]
3279: [--keyid <keyid>]
3280:
3281: ipsec whack --scdecrypt <data>
3282: [--inbase 16|hex|64|base64|256|text|ascii]
3283: [--outbase 16|hex|64|base64|256|text|ascii]
3284: [--keyid <keyid>]
3285:
3286: The default setting for inbase and outbase is hex.
3287:
3288: The new proxy interface can be used for securing symmetric
3289: encryption keys required by the cryptoloop or dm-crypt
3290: disk encryption schemes, especially in the case when
3291: pkcs11keepstate=yes causes pluto to lock the pkcs11 slot
3292: permanently.
3293:
3294: - if the file /etc/ipsec.secrets is lacking during the startup of
3295: pluto then the root-readable file /etc/ipsec.d/private/myKey.der
3296: containing a 2048 bit RSA private key and a matching self-signed
3297: certificate stored in the file /etc/ipsec.d/certs/selfCert.der
3298: is automatically generated by calling the function
3299:
3300: ipsec scepclient --out pkcs1 --out cert-self
3301:
3302: scepclient was written by Jan Hutter and Martin Willi, students
3303: at the University of Applied Sciences in Rapperswil, Switzerland.
3304:
3305:
3306: strongswan-2.5.4
3307: ----------------
3308:
3309: - the current extension of the PKCS#7 framework introduced
3310: a parsing error in PKCS#7 wrapped X.509 certificates that are
3311: e.g. transmitted by Windows XP when multi-level CAs are used.
3312: the parsing syntax has been fixed.
3313:
3314: - added a patch by Gerald Richter which tolerates multiple occurrences
3315: of the ipsec0 interface when using KLIPS.
3316:
3317:
3318: strongswan-2.5.3
3319: ----------------
3320:
3321: - with gawk-3.1.4 the word "default2 has become a protected
3322: keyword for use in switch statements and cannot be used any
3323: more in the strongSwan scripts. This problem has been
3324: solved by renaming "default" to "defaults" and "setdefault"
3325: in the scripts _confread and auto, respectively.
3326:
3327: - introduced the parameter leftsendcert with the values
3328:
3329: always|yes (the default, always send a cert)
3330: ifasked (send the cert only upon a cert request)
3331: never|no (never send a cert, used for raw RSA keys and
3332: self-signed certs)
3333:
3334: - fixed the initialization of the ESP key length to a default of
3335: 128 bits in the case that the peer does not send a key length
3336: attribute for AES encryption.
3337:
3338: - applied Herbert Xu's uniqueIDs patch
3339:
3340: - applied Herbert Xu's CLOEXEC patches
3341:
3342:
3343: strongswan-2.5.2
3344: ----------------
3345:
3346: - CRLs can now be cached also in the case when the issuer's
3347: certificate does not contain a subjectKeyIdentifier field.
3348: In that case the subjectKeyIdentifier is computed by pluto as the
3349: 160 bit SHA-1 hash of the issuer's public key in compliance
3350: with section 4.2.1.2 of RFC 3280.
3351:
3352: - Fixed a bug introduced by strongswan-2.5.1 which eliminated
3353: not only multiple Quick Modes of a given connection but also
3354: multiple connections between two security gateways.
3355:
3356:
3357: strongswan-2.5.1
3358: ----------------
3359:
3360: - Under the native IPsec of the Linux 2.6 kernel, a %trap eroute
3361: installed either by setting auto=route in ipsec.conf or by
3362: a connection put into hold, generates an XFRM_ACQUIRE event
3363: for each packet that wants to use the not-yet existing
3364: tunnel. Up to now each XFRM_ACQUIRE event led to an entry in
3365: the Quick Mode queue, causing multiple IPsec SA to be
3366: established in rapid succession. Starting with strongswan-2.5.1
3367: only a single IPsec SA is established per host-pair connection.
3368:
3369: - Right after loading the PKCS#11 module, all smartcard slots are
3370: searched for certificates. The result can be viewed using
3371: the command
3372:
3373: ipsec auto --listcards
3374:
3375: The certificate objects found in the slots are numbered
3376: starting with #1, #2, etc. This position number can be used to address
3377: certificates (leftcert=%smartcard) and keys (: PIN %smartcard)
3378: in ipsec.conf and ipsec.secrets, respectively:
3379:
3380: %smartcard (selects object #1)
3381: %smartcard#1 (selects object #1)
3382: %smartcard#3 (selects object #3)
3383:
3384: As an alternative the existing retrieval scheme can be used:
3385:
3386: %smartcard:45 (selects object with id=45)
3387: %smartcard0 (selects first object in slot 0)
3388: %smartcard4:45 (selects object in slot 4 with id=45)
3389:
3390: - Depending on the settings of CKA_SIGN and CKA_DECRYPT
3391: private key flags either C_Sign() or C_Decrypt() is used
3392: to generate a signature.
3393:
3394: - The output buffer length parameter siglen in C_Sign()
3395: is now initialized to the actual size of the output
3396: buffer prior to the function call. This fixes the
3397: CKR_BUFFER_TOO_SMALL error that could occur when using
3398: the OpenSC PKCS#11 module.
3399:
3400: - Changed the initialization of the PKCS#11 CK_MECHANISM in
3401: C_SignInit() to mech = { CKM_RSA_PKCS, NULL_PTR, 0 }.
3402:
3403: - Refactored the RSA public/private key code and transferred it
3404: from keys.c to the new pkcs1.c file as a preparatory step
3405: towards the release of the SCEP client.
3406:
3407:
3408: strongswan-2.5.0
3409: ----------------
3410:
3411: - The loading of a PKCS#11 smartcard library module during
3412: runtime does not require OpenSC library functions any more
3413: because the corresponding code has been integrated into
3414: smartcard.c. Also the RSAREF pkcs11 header files have been
3415: included in a newly created pluto/rsaref directory so that
3416: no external include path has to be defined any longer.
3417:
3418: - A long-awaited feature has been implemented at last:
3419: The local caching of CRLs fetched via HTTP or LDAP, activated
3420: by the parameter cachecrls=yes in the config setup section
3421: of ipsec.conf. The dynamically fetched CRLs are stored under
3422: a unique file name containing the issuer's subjectKeyID
3423: in /etc/ipsec.d/crls.
3424:
3425: - Applied a one-line patch courtesy of Michael Richardson
3426: from the Openswan project which fixes the kernel-oops
3427: in KLIPS when an snmp daemon is running on the same box.
3428:
3429:
3430: strongswan-2.4.4
3431: ----------------
3432:
3433: - Eliminated null length CRL distribution point strings.
3434:
3435: - Fixed a trust path evaluation bug introduced with 2.4.3
3436:
3437:
3438: strongswan-2.4.3
3439: ----------------
3440:
3441: - Improved the joint OCSP / CRL revocation policy.
3442: OCSP responses have precedence over CRL entries.
3443:
3444: - Introduced support of CRLv2 reason codes.
3445:
3446: - Fixed a bug with key-pad equipped readers which caused
3447: pluto to prompt for the pin via the console when the first
3448: occasion to enter the pin via the key-pad was missed.
3449:
3450: - When pluto is built with LDAP_V3 enabled, the library
3451: liblber required by newer versions of openldap is now
3452: included.
3453:
3454:
3455: strongswan-2.4.2
3456: ----------------
3457:
3458: - Added the _updown_espmark template which requires all
3459: incoming ESP traffic to be marked with a default mark
3460: value of 50.
3461:
3462: - Introduced the pkcs11keepstate parameter in the config setup
3463: section of ipsec.conf. With pkcs11keepstate=yes the PKCS#11
3464: session and login states are kept as long as possible during
3465: the lifetime of pluto. This means that a PIN entry via a key
3466: pad has to be done only once.
3467:
3468: - Introduced the pkcs11module parameter in the config setup
3469: section of ipsec.conf which specifies the PKCS#11 module
3470: to be used with smart cards. Example:
3471:
3472: pkcs11module=/usr/lib/pkcs11/opensc-pkcs11.lo
3473:
3474: - Added support of smartcard readers equipped with a PIN pad.
3475:
3476: - Added patch by Jay Pfeifer which detects when netkey
3477: modules have been statically built into the Linux 2.6 kernel.
3478:
3479: - Added two patches by Herbert Xu. The first uses ip xfrm
3480: instead of setkey to flush the IPsec policy database. The
3481: second sets the optional flag in inbound IPComp SAs only.
3482:
3483: - Applied Ulrich Weber's patch which fixes an interoperability
3484: problem between native IPsec and KLIPS systems caused by
3485: setting the replay window to 32 instead of 0 for ipcomp.
3486:
3487:
3488: strongswan-2.4.1
3489: ----------------
3490:
3491: - Fixed a bug which caused an unwanted Mode Config request
3492: to be initiated in the case where "right" was used to denote
3493: the local side in ipsec.conf and "left" the remote side,
3494: contrary to the recommendation that "right" be remote and
3495: "left" be"local".
3496:
3497:
3498: strongswan-2.4.0a
3499: -----------------
3500:
3501: - updated Vendor ID to strongSwan-2.4.0
3502:
3503: - updated copyright statement to include David Buechi and
3504: Michael Meier
3505:
3506:
3507: strongswan-2.4.0
3508: ----------------
3509:
3510: - strongSwan now communicates with attached smartcards and
3511: USB crypto tokens via the standardized PKCS #11 interface.
3512: By default the OpenSC library from www.opensc.org is used
3513: but any other PKCS#11 library could be dynamically linked.
3514: strongSwan's PKCS#11 API was implemented by David Buechi
3515: and Michael Meier, both graduates of the Zurich University
3516: of Applied Sciences in Winterthur, Switzerland.
3517:
3518: - When a %trap eroute is triggered by an outgoing IP packet
3519: then the native IPsec stack of the Linux 2.6 kernel [often/
3520: always?] returns an XFRM_ACQUIRE message with an undefined
3521: protocol family field and the connection setup fails.
3522: As a workaround IPv4 (AF_INET) is now assumed.
3523:
3524: - the results of the UML test scenarios are now enhanced
3525: with block diagrams of the virtual network topology used
3526: in a particular test.
3527:
3528:
3529: strongswan-2.3.2
3530: ----------------
3531:
3532: - fixed IV used to decrypt informational messages.
3533: This bug was introduced with Mode Config functionality.
3534:
3535: - fixed NCP Vendor ID.
3536:
3537: - undid one of Ulrich Weber's maximum udp size patches
3538: because it caused a segmentation fault with NAT-ed
3539: Delete SA messages.
3540:
3541: - added UML scenarios wildcards and attr-cert which
3542: demonstrate the implementation of IPsec policies based
3543: on wildcard parameters contained in Distinguished Names and
3544: on X.509 attribute certificates, respectively.
3545:
3546:
3547: strongswan-2.3.1
3548: ----------------
3549:
3550: - Added basic Mode Config functionality
3551:
3552: - Added Mathieu Lafon's patch which upgrades the status of
3553: the NAT-Traversal implementation to RFC 3947.
3554:
3555: - The _startklips script now also loads the xfrm4_tunnel
3556: module.
3557:
3558: - Added Ulrich Weber's netlink replay window size and
3559: maximum udp size patches.
3560:
3561: - UML testing now uses the Linux 2.6.10 UML kernel by default.
3562:
3563:
3564: strongswan-2.3.0
3565: ----------------
3566:
3567: - Eric Marchionni and Patrik Rayo, both recent graduates from
3568: the Zuercher Hochschule Winterthur in Switzerland, created a
3569: User-Mode-Linux test setup for strongSwan. For more details
3570: please read the INSTALL and README documents in the testing
3571: subdirectory.
3572:
3573: - Full support of group attributes based on X.509 attribute
3574: certificates. Attribute certificates can be generated
3575: using the openac facility. For more details see
3576:
3577: man ipsec_openac.
3578:
3579: The group attributes can be used in connection definitions
3580: in order to give IPsec access to specific user groups.
3581: This is done with the new parameter left|rightgroups as in
3582:
3583: rightgroups="Research, Sales"
3584:
3585: giving access to users possessing the group attributes
3586: Research or Sales, only.
3587:
3588: - In Quick Mode clients with subnet mask /32 are now
3589: coded as IP_V4_ADDRESS or IP_V6_ADDRESS. This should
3590: fix rekeying problems with the SafeNet/SoftRemote and NCP
3591: Secure Entry Clients.
3592:
3593: - Changed the defaults of the ikelifetime and keylife parameters
3594: to 3h and 1h, respectively. The maximum allowable values are
3595: now both set to 24 h.
3596:
3597: - Suppressed notification wars between two IPsec peers that
3598: could e.g. be triggered by incorrect ISAKMP encryption.
3599:
3600: - Public RSA keys can now have identical IDs if either the
3601: issuing CA or the serial number is different. The serial
3602: number of a certificate is now shown by the command
3603:
3604: ipsec auto --listpubkeys
3605:
3606:
3607: strongswan-2.2.2
3608: ----------------
3609:
3610: - Added Tuomo Soini's sourceip feature which allows a strongSwan
3611: roadwarrior to use a fixed Virtual IP (see README section 2.6)
3612: and reduces the well-known four tunnel case on VPN gateways to
3613: a single tunnel definition (see README section 2.4).
3614:
3615: - Fixed a bug occurring with NAT-Traversal enabled when the responder
3616: suddenly turns initiator and the initiator cannot find a matching
3617: connection because of the floated IKE port 4500.
3618:
3619: - Removed misleading ipsec verify command from barf.
3620:
3621: - Running under the native IP stack, ipsec --version now shows
3622: the Linux kernel version (courtesy to the Openswan project).
3623:
3624:
3625: strongswan-2.2.1
3626: ----------------
3627:
3628: - Introduced the ipsec auto --listalgs monitoring command which lists
3629: all currently registered IKE and ESP algorithms.
3630:
3631: - Fixed a bug in the ESP algorithm selection occurring when the strict flag
3632: is set and the first proposed transform does not match.
3633:
3634: - Fixed another deadlock in the use of the lock_certs_and_keys() mutex,
3635: occurring when a smartcard is present.
3636:
3637: - Prevented that a superseded Phase1 state can trigger a DPD_TIMEOUT event.
3638:
3639: - Fixed the printing of the notification names (null)
3640:
3641: - Applied another of Herbert Xu's Netlink patches.
3642:
3643:
3644: strongswan-2.2.0
3645: ----------------
3646:
3647: - Support of Dead Peer Detection. The connection parameter
3648:
3649: dpdaction=clear|hold
3650:
3651: activates DPD for the given connection.
3652:
3653: - The default Opportunistic Encryption (OE) policy groups are not
3654: automatically included anymore. Those wishing to activate OE can include
3655: the policy group with the following statement in ipsec.conf:
3656:
3657: include /etc/ipsec.d/examples/oe.conf
3658:
3659: The default for [right|left]rsasigkey is now set to %cert.
3660:
3661: - strongSwan now has a Vendor ID of its own which can be activated
3662: using the compile option VENDORID
3663:
3664: - Applied Herbert Xu's patch which sets the compression algorithm correctly.
3665:
3666: - Applied Herbert Xu's patch fixing an ESPINUDP problem
3667:
3668: - Applied Herbert Xu's patch setting source/destination port numbers.
3669:
3670: - Reapplied one of Herbert Xu's NAT-Traversal patches which got
3671: lost during the migration from SuperFreeS/WAN.
3672:
3673: - Fixed a deadlock in the use of the lock_certs_and_keys() mutex.
3674:
3675: - Fixed the unsharing of alg parameters when instantiating group
3676: connection.
3677:
3678:
3679: strongswan-2.1.5
3680: ----------------
3681:
3682: - Thomas Walpuski made me aware of a potential DoS attack via
3683: a PKCS#7-wrapped certificate bundle which could overwrite valid CA
3684: certificates in Pluto's authority certificate store. This vulnerability
3685: was fixed by establishing trust in CA candidate certificates up to a
3686: trusted root CA prior to insertion into Pluto's chained list.
3687:
3688: - replaced the --assign option by the -v option in the auto awk script
3689: in order to make it run with mawk under debian/woody.
3690:
3691:
3692: strongswan-2.1.4
3693: ----------------
3694:
3695: - Split of the status information between ipsec auto --status (concise)
3696: and ipsec auto --statusall (verbose). Both commands can be used with
3697: an optional connection selector:
3698:
3699: ipsec auto --status[all] <connection_name>
3700:
3701: - Added the description of X.509 related features to the ipsec_auto(8)
3702: man page.
3703:
3704: - Hardened the ASN.1 parser in debug mode, especially the printing
3705: of malformed distinguished names.
3706:
3707: - The size of an RSA public key received in a certificate is now restricted to
3708:
3709: 512 bits <= modulus length <= 8192 bits.
3710:
3711: - Fixed the debug mode enumeration.
3712:
3713:
3714: strongswan-2.1.3
3715: ----------------
3716:
3717: - Fixed another PKCS#7 vulnerability which could lead to an
3718: endless loop while following the X.509 trust chain.
3719:
3720:
3721: strongswan-2.1.2
3722: ----------------
3723:
3724: - Fixed the PKCS#7 vulnerability discovered by Thomas Walpuski
3725: that accepted end certificates having identical issuer and subject
3726: distinguished names in a multi-tier X.509 trust chain.
3727:
3728:
3729: strongswan-2.1.1
3730: ----------------
3731:
3732: - Removed all remaining references to ipsec_netlink.h in KLIPS.
3733:
3734:
3735: strongswan-2.1.0
3736: ----------------
3737:
3738: - The new "ca" section allows to define the following parameters:
3739:
3740: ca kool
3741: cacert=koolCA.pem # cacert of kool CA
3742: ocspuri=http://ocsp.kool.net:8001 # ocsp server
3743: ldapserver=ldap.kool.net # default ldap server
3744: crluri=http://www.kool.net/kool.crl # crl distribution point
3745: crluri2="ldap:///O=Kool, C= .." # crl distribution point #2
3746: auto=add # add, ignore
3747:
3748: The ca definitions can be monitored via the command
3749:
3750: ipsec auto --listcainfos
3751:
3752: - Fixed cosmetic corruption of /proc filesystem by integrating
3753: D. Hugh Redelmeier's freeswan-2.06 kernel fixes.
3754:
3755:
3756: strongswan-2.0.2
3757: ----------------
3758:
3759: - Added support for the 818043 NAT-Traversal update of Microsoft's
3760: Windows 2000/XP IPsec client which sends an ID_FQDN during Quick Mode.
3761:
3762: - A symbolic link to libcrypto is now added in the kernel sources
3763: during kernel compilation
3764:
3765: - Fixed a couple of 64 bit issues (mostly casts to int).
3766: Thanks to Ken Bantoft who checked my sources on a 64 bit platform.
3767:
3768: - Replaced s[n]printf() statements in the kernel by ipsec_snprintf().
3769: Credits go to D. Hugh Redelmeier, Michael Richardson, and Sam Sgro
3770: of the FreeS/WAN team who solved this problem with the 2.4.25 kernel.
3771:
3772:
3773: strongswan-2.0.1
3774: ----------------
3775:
3776: - an empty ASN.1 SEQUENCE OF or SET OF object (e.g. a subjectAltName
3777: certificate extension which contains no generalName item) can cause
3778: a pluto crash. This bug has been fixed. Additionally the ASN.1 parser has
3779: been hardened to make it more robust against malformed ASN.1 objects.
3780:
3781: - applied Herbert Xu's NAT-T patches which fixes NAT-T under the native
3782: Linux 2.6 IPsec stack.
3783:
3784:
3785: strongswan-2.0.0
3786: ----------------
3787:
3788: - based on freeswan-2.04, x509-1.5.3, nat-0.6c, alg-0.8.1rc12
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/cvsweb/back.gif){kind=icon}
Return to NEWS CVS log ![[TXT]](/icons/cvsweb/text.gif){kind=icon}
![[DIR]](/icons/cvsweb/dir.gif){kind=icon}
Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / strongswan