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