Download strongSwan 5.7.0

Various protocols can be used to secure connections over public networks, such as the widely used ipsec. StrongSwan is an ipsec implementation for Android, Linux, FreeBSD, iOS and macOS systems. Support for ikev1, ikev2, and ipv6 is provided, as on this page can be read. The developers have released strongSwan 5.7.0 with the following changes:

Version 5.7.0

• Fixes a potential authorization bypass vulnerability in the gmp plugin that was caused by a too lenient verification of PKCS#1 v1.5 signatures. Several flaws could be exploited by a Bleichenbacher-style attack to forge signatures for low-exponent keys (ie with e=3).
  CVE-2018-16151 has been assigned to the problem of accepting random bytes after the OID of the hash function in such signatures, and CVE-2018-16152 has been assigned to the issue of not verifying that the parameters in the ASN.1 algorithmIdentitifer structure is empty. Other flaws that don’t lead to a vulnerability directly (eg not checking for at least 8 bytes of padding) have no separate CVE assigned. Please refer to our blog for details.
• Dots are not allowed anymore in section names in swanctl.conf and strongswan.conf. This mainly affects the configuration of file loggers. If the path for such a log file contains dots it now has to be configured in the new path setting within the arbitrarily renamed subsection in the filelog section.
• Sections in swanctl.conf and strongswan.conf may now reference other sections. All settings and subsections from such a section are inherited. This allows to simplify configs as redundant information has only to be specified once and may then be included in other sections (see strongswan.conf for an example).
• The originally selected IKE config (based on the IPs and IKE version) can now change if no matching algorithm proposal is found. This way the order of the configs doesn’t matter that much anymore and it’s easily possible to specify separate configs for clients that require weaker algorithms (instead of having to also add them in other configs that might be selected).
• Support for Postquantum Preshared Keys for IKEv2 (draft-ietf-ipsecme-qr-ikev2) has been added. For an example refer to the swanctl/rw-cert-ppk scenario (or with EAP, or PSK authentication).
• The new botan plugin is a wrapper around the Botan C++ crypto library. It requires a fairly recent build from Botan’s master branch (or the upcoming 2.8.0 release). Thanks to René Korthaus and his team from Rohde & Schwarz Cybersecurity for the initial patch and to Jack Lloyd for quickly adding missing functions to Botan’s FFI (C89) interface.
• Implementation of RFC 8412 “Software Inventory Message and Attributes (SWIMA) for PA-TNC”. SWIMA subscription option sets CLOSE_WRITE trigger on apt history.log file resulting in a ClientRetry PB-TNC batch to initialize a new measurement cycle. The new imv/imc-swid plugins replace the previous imv/imc-swid plugins, which were removed.
• Added support for fuzzing the PA-TNC (RFC 5792) and PB-TNC (RFC 5793) NEA protocols on Google’s OSS-Fuzz infrastructure.
• Support for version 2 of Intel’s TPM2-TSS TGC Software Stack. The presence of the in-kernel /dev/tpmrm0 resource manager is automatically detected.
• The pki tool accepts a xmppAddr otherName as a subjectAlternativeName using the syntax –san xmppaddr:#&060;jid>.
• swanctl.conf supports the configuration of marks the in- and/or outbound SA should apply to packets after processing on Linux. Configuring such a mark for outbound SAs requires at least a 4.14 kernel. The ability to set a mask and configuring a mark/mask for inbound SAs will be added with the upcoming 4.19 kernel.
• New options in swanctl.conf allow configuring how/whether DF, ECN and DS fields in the IP headers are copied during IPsec processing. Controlling this is currently only possible on Linux.
• The handling of sequence numbers in IKEv1 DPDs has been improved (#2714).
• To avoid conflicts, the dhcp plugin now only uses the DHCP server port if explicitly configured.