Changelog for strongswan-ipsec-5.9.14-lp156.155.2.x86_64.rpm :

* Thu Jun 20 2024 Dominique Leuenberger - Update description of ipsec package: no longer mention /etc/init.d, which is not there for a long time anymore.- Drop legacy rc
* -> sbin/service symlink. This was compatibilty boilerplate to transparently move between SySV and systemd [jsc#PED-264].
* Tue Mar 19 2024 Jan Engelhardt - Update to release 5.9.14
* Support for the IKEv2 OCSP extensions (RFC 4806) has been added, which allows peers to request and send OCSP responses directly in IKEv2.
* Validation of X.509 name constraints in the constraints plugin has been refactored to align with RFC 5280.
* Fail SA installation on Linux if replay protection is disabled while ESN is enabled, which the kernel currently doesn\'t support.
* Mon Feb 26 2024 Dominique Leuenberger - Use %patch -P N instead of deprecated %patchN.
* Fri Dec 01 2023 Jan Engelhardt - Update to release 5.9.13
* OCSP error responses are now dropped immediately instead of trying to verify a non-existent signature.
* Mon Nov 20 2023 Jan Engelhardt - Update to release 5.9.12
* Fixed a buffer overflow in charon-tkm [CVEV-2023-41913]
* Support for ``nameConstraints`` of type ``iPAddress`` are now supported by the \"x509\", \"openssl\" and \"constraints\" plugins
* Support for encoding subjectAlternativeName extensions of type uniformResourceIdentifier in X.509 certificates has been added.
* Make the NetworkManager plugin (charon-nm) actually use the XFRM interface it creates since 5.9.10. This involves setting interface IDs on SAs and policies, and installing routes via the interface. To avoid routing loops if the remote traffic selectors include the VPN server, IKE and ESP packets are marked to bypass the routing table that contains the routes via XFRM interface.
* The kernel-libipsec plugin now always installs routes to remote networks even if no address is found in the local traffic selectors, which allows forwarding traffic from networks the VPN host is not part of.
* Fixed issues while reestablishing multiple CHILD_SAs (e.g. after a DPD timeout) that could cause a reqid to get assigned to multiple CHILD_SAs with unrelated traffic selectors.
* Thu Jun 22 2023 Mohd Saquib - Removed .hmac files + hmac integrity check logic from strongswan-hmac package as it is not mandated anymore by FIPS (boo#1185116)- Removed folliwng files: [- strongswan_fipscheck.patch] [- fipscheck.sh.in] Note: strongswan-hmac package is not removed as it still provides a config file that doesn\'t allow non-fips approved algorithms
* Mon Jun 12 2023 Jan Engelhardt - Remove pre-SLE15 build logic
* Mon Jun 12 2023 Mohd Saquib - Update to release 5.9.11
* A deadlock in the vici plugin has been fixed
* Per RFC 5280, CRLs now have to be signed by a certificate that either encodes the cRLSign keyUsage bit (even if it is a CA certificate), or is a CA certificate without a keyUsage extension.
* Support for optional CA labels in EST server URIs was added to the pki --est and pki --estca commands.
* The pkcs7 and openssl plugins now support CMS-style signatures in PKCS#7 containers, which allows verifying RSA-PSS and ECDSA signatures.
* Fixed a regression in the server implementation of EAP-TLS when using TLS <=1.2.
* The EAP-TLS client does now enforce that the TLS handshake is complete when using TLS <=1.2.
* On Linux, the kernel-libipsec plugin can now optionally handle ESP packets without UDP encapsulation.
* The dhcp plugin uses an alternative method to determine the source address when sending unicast DHCP requests.
* ECDSA and EdDSA public keys are supported by the ipseckey plugin when parsing RFC 4025 IPSECKEY resource records.
* Wed Apr 05 2023 Mohd Saquib - Allow to use stroke aka ipsec interface by default instead of vici aka swanctl interface which is current upstream\'s default. strongswan.service which enables swanctl interface is masked to stop interfering with the ipsec interface (bsc#1184144)- Removes deprecated SysV support
* Thu Mar 02 2023 Jan Engelhardt - Update to release 5.9.10
* Fixed a vulnerability related to certificate verification in TLS-based EAP methods that leads to an authentication bypass followed by an expired pointer dereference that results in a denial of service but possibly even remote code execution. [CVE-2023-26463]
* Added support for full packet hardware offload for IPsec SAs and policies, which has been introduced with the Linux 6.2 kernel, to the kernel-netlink plugin. Bypass policies for the IKE ports are automatically offloaded to devices that support this type of offloading.
* TLS-based EAP methods use the key derivation specified in draft-ietf-emu-tls-eap-types when used with TLS 1.3.
* Routes via XFRM interfaces can now optionally be installed automatically by enabling the charon.plugins.kernel-netlink.install_routes_xfrmi option.- If connections are missing in `ipsec status`, check that strongswan-starter.service (rather than strongswan.service) is active.- Remove CVE-2023-26463_tls_auth_bypass_exp_pointer.patch
* Thu Mar 02 2023 Mohd Saquib - Added patch to fix a vulnerability in incorrectly accepted untrusted public key with incorrect refcount (CVE-2023-26463 boo#1208608) [+ CVE-2023-26463_tls_auth_bypass_exp_pointer.patch]
* Tue Jan 03 2023 Jan Engelhardt - Update to release 5.9.9
* Fixed an issue that could cause OCSP requests to contain an incorrect serial number if the openssl plugin parsed the certificate.
* The resolve plugin does not invoke resolvconf(8) with individual interface names for each name server anymore.
* The kernel-netlink plugin now logs extended ACK error and warning messages provided by the Linux kernel if e.g. the installation of an SA or policy fails.
* Mon Oct 03 2022 Jan Engelhardt - Update to release 5.9.8
* Fixed a vulnerability related to online certificate revocation checking that was caused because the revocation plugin used potentially untrusted OCSP URIs and CRL distribution points in certificates.
* The `pki --scep/--scepca` commands implement the HTTP-based \"Simple Certificate Enrollment Protocol\" (RFC 8894 SCEP) replacing the old and long deprecated scepclient that has been removed.
* The `pki --est|estca` commands implement the HTTPS-based \"Enrollment over Secure Transport\" (RFC 7070 EST) protocol.
* The TLS client implementation now sends an empty certificate payload if a certificate request is received but no certificate is available.
* The socket plugins don\'t set the SO_REUSEADDR option anymore on the IKE UDP sockets, so an error is triggered if e.g. two daemons (e.g. charon and charon-systemd) are running concurrently using the same ports.
* Sat Jul 30 2022 Peter Conrad - Update to release 5.9.7
* The IKEv2 key derivation is now delayed until the keys are actually needed to process or send the next message.
* Inbound IKEv2 messages, in particular requests, are now processed differently.
* The retransmission logic in the dhcp plugin has been fixed.
* The connmark plugin now considers configured masks in installed firewall rules.
* Child config selection has been fixed as responder in cases where multiple children use transport mode traffic selectors.
* The outbound SA/policy is now also removed after IKEv1 CHILD_SA rekeyings.
* The openssl plugin supports AES and Camellia in CTR mode.
* The AES-XCBC/CMAC PRFs are demoted in the default proposal (after HMAC-based PRFs) since they were never widely adopted.
* The kdf plugin is now automatically enabled if any of the aesni, cmac or xcbc plugins are enabled, or if none of the plugins that directly provide HMAC-based KDFs are enabled.
* Sat Apr 30 2022 Jan Engelhardt - Update to release 5.9.6
* Support for labeled IPsec with IKEv2 (draft-ietf-ipsecme-labeled-ipsec) has been added. Two modes are currently supported.
* The secrets used for generating COOKIE payloads are now switched based on a time limit (2 minutes) and not the previous usage limit (10\'000 generated cookies).
* Actively initiating duplicate CHILD_SAs within the same IKE_SA is now largely prevented.
* If the source address is unknown when initiating an IKEv2 SA, a NAT situation is now forced for IPv4 (for IPv6, NAT-T is disabled) to avoid causing asymmetric enabling of UDP-encapsulation.
* The main two steps of the IKEv2 key derivation (PRF/prf+) have been modularized. In particular, prf+ is now provided by a plugin.- Drop prf-plus-modularization.patch
* Wed Mar 16 2022 Marcus Meissner - prf-plus-modularization.patch: updated from upstream branch after certifier feedback, SKEYSEED generated via HKDF-Extract.
* Thu Mar 03 2022 Marcus Meissner - Added prf-plus-modularization.patch that outsources the IKE key derivation to openssl. (will be merged to 5.9.6)- package the kdf config, template and plugin
* Wed Jan 26 2022 Jan Engelhardt - Update to release 5.9.5
* Fixed a vulnerability in the EAP client implementation (CVE-2021-45079 bsc#1194471).
* libtpmtss may now establish a secure session via RSA OAEP public key encryption or an ephemeral ECDH key exchange, respectively.
* When rekeying CHILD_SAs, the old outbound SA is now uninstalled earlier on the initiator/winner.
* The openssl plugin now only announces the ECDH groups actually supported by OpenSSL (determined via EC_get_builtin_curves()).
* Added support for AES-CFB.
* Wed Nov 24 2021 Johannes Segitz - Added hardening to systemd service(s) (bsc#1181400). Added patch(es):
* harden_strongswan.service.patch
* Mon Nov 22 2021 Bjørn Lie - Update to version 5.9.4:
* Fixed a denial-of-service vulnerability in the gmp plugin that was caused by an integer overflow when processing RSASSA-PSS signatures with very large salt lengths. This vulnerability has been registered as CVE-2021-41990. Please refer to our blog for details. (bsc#1191367)
* Fixed a denial-of-service vulnerability in the in-memory certificate cache if certificates are replaced and a very large random value caused an integer overflow. This vulnerability has been registered as CVE-2021-41991. Please refer to our blog for details. (bsc#1191435)
* Fixed a related flaw that caused the daemon to accept and cache an infinite number of versions of a valid certificate by modifying the parameters in the signatureAlgorithm field of the outer X.509 Certificate structure.
* AUTH_LIFETIME notifies are now only sent by a responder if it can\'t reauthenticate the IKE_SA itself due to asymmetric authentication (i.e. EAP) or the use of virtual IPs.
* Several corner cases with reauthentication have been fixed (48fbe1d, 36161fe, 0d373e2).
* Serial number generation in several pki sub-commands has been fixed so they don\'t start with an unintended zero byte.
* Loading SSH public keys via vici has been improved.
* Shared secrets, PEM files, vici messages, PF_KEY messages, swanctl configs and other data is properly wiped from memory.
* Use a longer dummy key to initialize HMAC instances in the openssl plugin in case it\'s used in FIPS-mode.
* The --enable-tpm option now implies --enable-tss-tss2 as the plugin doesn\'t do anything without a TSS 2.0.
* libtpmtss is initialized in all programs and libraries that use it.
* Migrated testing scripts to Python 3.
* Mon Sep 27 2021 Bjørn Lie - Update to version 5.9.3:
* Added AES-ECB, SHA-3 and SHAKE-256 support to the wolfssl plugin.
* Added AES-CCM support to the openssl plugin (#353 bsc#1185363).
* The x509 and the openssl plugins now consider the authorityKeyIdentifier, if available, before verifying signatures, which avoids unnecessary signature verifications after a CA key rollover if both CA certificates are loaded. The openssl plugin now does the same also for CRLs (the x509 plugin already did).
* The pkcs11 plugin better handles optional attributes like CKA_TRUSTED, which previously depended on a version check.
* The NetworkManager backend (charon-nm) now supports using SANs as client identities, not only full DNs (#437).
* charon-tkm now handles IKE encryption.
* Send a MOBIKE update again if a a change in the NAT mappings is detected but the endpoints stay the same (e143a7d).
* A deadlock in the HA plugin introduced with 5.9.2 has been fixed (#456).
* DSCP values are now also set for NAT keepalives.
* The ike_derived_keys() hook now receives more keys but in a different order (4e29d6f).
* Converted most of the test case scenarios to the vici interface.- Replace libsoup-devel with pkgconfig(libsoup-2.4) BuildRequires, as this is what really checks for. Needed as libsoup-3.0 is released.- 5.9.1 - README: added a missing \" to pki example command (bsc#1167880) - fixed a libgcrypt call in FIPS mode (bsc#1180801)
* Mon Sep 07 2020 Jan Engelhardt - Update to release 5.9.0
* Prefer AEAD algorithms for ESP; this puts AES-GCM in a default AEAD proposal in front of the previous default proposal.
* If a connection fails after getting redirected, we now restart connecting to the original host, not the one redirected to.
* For peers that don\'t send the EAP_ONLY_AUTHENTICATION notify but still expect to use EAP-only authentication, the charon.force_eap_only_authentication option can be enabled to force this type of authentication even on non-compliant peers.
* IPv6 virtual IPs are now always enumerated, ignoring the charon.prefer_temporary_addrs setting, which should fix route installation if the latter is enabled.
* Tue Sep 01 2020 Jan Engelhardt - Enable bypass-lan strongswan plugin
* Fri May 01 2020 Bjørn Lie - Update to version 5.8.4:
* In IKEv1 Quick Mode make sure that a proposal exists before determining lifetimes (fixes a crash due to a null-pointer dereference in 5.8.3).
* OpenSSL currently doesn\'t support squeezing bytes out of a SHAKE128/256 XOF (support was added with 5.8.3) multiple times. Unfortunately, EVP_DigestFinalXOF() completely resets the context and later calls not simply fail, they cause a null-pointer dereference in libcrypto. c5c1898d73 fixes the crash at the cost of repeating initializing the whole state and allocating too much data for subsequent calls (hopefully, once the OpenSSL issue 7894 is resolved we can implement this more efficiently).
* On 32-bit platforms, reading arbitrary 32-bit integers from config files (e.g. for charon.spi_min/max) has been fixed.
* charon-nm now allows using fixed source ports.- Changes from version 5.8.3:
* Updates for the NM plugin (and backend, which has to be updated to be compatible): + EAP-TLS authentication (#2097) + Certificate source (file, agent, smartcard) is selectable independently + Add support to configure local and remote identities (#2581) + Support configuring a custom server port (#625) + Show hint regarding password storage policy + Replaced the term \"gateway\" with \"server\" + Fixes build issues due to use of deprecated GLib macros/functions + Updated Glade file to GTK 3.2
* The NM backend now supports reauthentication and redirection.
* Previously used reqids are now reallocated, which works around an issue on FreeBSD where the kernel doesn\'t allow the daemon to use reqids > 16383 (#2315).
* On Linux, throw type routes are installed in table 220 for passthrough policies. The kernel will then fall back on routes in routing tables with lower priorities for matching traffic. This way, they require less information (e.g. no interface or source IP) and can be installed earlier and are not affected by updates.
* For IKEv1, the lifetimes of the actually selected transform are returned to the initiator, which is an issue if the peer uses different lifetimes for different transforms (#3329). We now also return the correct transform and proposal IDs (proposal ID was always 0, transform ID 1). IKE_SAs are now not re-established anymore (e.g. after several retransmits) if a deletion has been queued (#3335).
* Added support for Ed448 keys and certificates via openssl plugin and pki tool.
* Added support for SHA-3 and SHAKE128/256 in the openssl plugin.
* The use of algorithm IDs from the private use range can now be enabled globally, to use them even if no strongSwan vendor ID was exchanged (05e373aeb0).
* Fixed a compiler issue that may have caused invalid keyUsage extensions in certificates (#3249).
* A lot of spelling fixes.
* Fixed several reported issues.- Drop 0006-Resolve-multiple-definition-of-swanctl_dir.patch: Fixed upstream.
* Tue Mar 31 2020 Madhu Mohan Nelemane - Fix to resolve multiple definitions for swanctl_dir (bsc#1164493) [+ 0006-Resolve-multiple-definition-of-swanctl_dir.patch ]
* Mon Feb 17 2020 Johannes Kastl - move file %{_datadir}/dbus-1/system.d/nm-strongswan-service.conf to strongswan-nm subpackage, as it is needed for the NetworkManager plugin that uses strongswan-nm, not strongswan-ipsec This fixes the following error: ``` Failed to initialize a plugin instance: Connection \":1.153\" is not allowed to own the service \"org.freedesktop.NetworkManager.strongswan\" due to security policies in the configuration file ```
* Thu Jan 30 2020 Bjørn Lie - Drop upstream fixed patches:
* strongswan_modprobe_syslog.patch
* strongswan_fipsfilter.patch
* 0006-fix-compilation-error-by-adding-stdint.h.patch
* Sun Jan 26 2020 Jan Engelhardt - Replace %__-type macro indirections. Update homepage URL to https.
* Mon Jan 06 2020 Bjørn Lie - Update to version 5.8.2 (jsc#SLE-11370):
* The systemd service units have changed their name. \"strongswan\" is now \"strongswan-starter\", and \"strongswan-swanctl\" is now \"strongswan\". After installation, you need to `systemctl disable` the old name and `systemctl enable`+start the new one.
* Fix CVE-2018-17540, CVE-2018-16151 and CVE-2018-16152.
* boo#1109845 and boo#1107874.- Please check included NEWS file for info on what other changes that have been done in versions 5.8.2, 5.8.1 5.8.0, 5.7.2, 5.7.1 and 5.7.0.- Rebase strongswan_ipsec_service.patch.- Disable patches that need rebase or dropping:
* strongswan_modprobe_syslog.patch
* 0006-fix-compilation-error-by-adding-stdint.h.patch- Add conditional pkgconfig(libsystemd) BuildRequires: New dependency.
* Wed Jun 06 2018 bjorn.lieAATTgmail.com- Update to version 5.6.3 (CVE-2018-10811, boo#1093536, CVE-2018-5388, boo#1094462):
* Fixed a DoS vulnerability in the IKEv2 key derivation if the openssl plugin is used in FIPS mode and HMAC-MD5 is negotiated as PRF. This vulnerability has been registered as CVE-2018-10811, boo#1093536.
* Fixed a vulnerability in the stroke plugin, which did not check the received length before reading a message from the socket. Unless a group is configured, root privileges are required to access that socket, so in the default configuration this shouldn\'t be an issue. This vulnerability has been registered as CVE-2018-5388, boo#1094462.
* CRLs that are not yet valid are now ignored to avoid problems in scenarios where expired certificates are removed from new CRLs and the clock on the host doing the revocation check is trailing behind that of the host issuing CRLs. Not doing this could result in accepting a revoked and expired certificate, if it\'s still valid according to the trailing clock but not contained anymore in not yet valid CRLs.
* The issuer of fetched CRLs is now compared to the issuer of the checked certificate (#2608).
* CRL validation results other than revocation (e.g. a skipped check because the CRL couldn\'t be fetched) are now stored also for intermediate CA certificates and not only for end-entity certificates, so a strict CRL policy can be enforced in such cases.
* In compliance with RFC 4945, section 5.1.3.2, certificates used for IKE must now either not contain a keyUsage extension (like the ones generated by pki), or have at least one of the digitalSignature or nonRepudiation bits set.
* New options for vici/swanctl allow forcing the local termination of an IKE_SA. This might be useful in situations where it\'s known the other end is not reachable anymore, or that it already removed the IKE_SA, so retransmitting a DELETE and waiting for a response would be pointless.
* Waiting only a certain amount of time for a response (i.e. shorter than all retransmits would be) before destroying the IKE_SA is also possible by additionally specifying a timeout in the forced termination request.
* When removing routes, the kernel-netlink plugin now checks if it tracks other routes for the same destination and replaces the installed route instead of just removing it. Same during installation, where existing routes previously weren\'t replaced. This should allow using traps with virtual IPs on Linux (#2162).
* The dhcp plugin now only sends the client identifier DHCP option if the identity_lease setting is enabled (7b660944b6). It can also send identities of up to 255 bytes length, instead of the previous 64 bytes (30e886fe3b, 0e5b94d038). If a server address is configured, DHCP requests are now sent from port 67 instead of 68 to avoid ICMP port unreachables (becf027cd9).
* The handling of faulty INVALID_KE_PAYLOAD notifies (e.g. one containing a DH group that wasn\'t proposed) during CREATE_CHILD_SA exchanges has been improved (#2536).
* Roam events are now completely ignored for IKEv1 SAs (there is no MOBIKE to handle such changes properly).
* ChaCha20/Poly1305 is now correctly proposed without key length (#2614). For compatibility with older releases the chacha20poly1305compat keyword may be included in proposals to also propose the algorithm with a key length (c58434aeff).
* Configuration of hardware offload of IPsec SAs is now more flexible and allows a new setting (auto), which automatically uses it if the kernel and device both support it. If hw_offload is set to yes and offloading is not supported, the CHILD_SA installation now fails.
* The kernel-pfkey plugin optionally installs routes via internal interface (one with an IP in the local traffic selector). On FreeBSD, enabling this selects the correct source IP when sending packets from the gateway itself (e811659323).
* SHA-2 based PRFs are supported in PKCS#8 files as generated by OpenSSL 1.1 (#2574).
* The pki --verify tool may load CA certificates and CRLs from directories.
* The IKE daemon now also switches to port 4500 if the remote port is not 500 (e.g. because the remote maps the response to a different port, as might happen on Azure), as long as the local port is 500 (85bfab621d).
* Fixed an issue with DNS servers passed to NetworkManager in charon-nm (ee8c25516a).
* Logged traffic selectors now always contain the protocol if either protocol or port are set (a36d8097ed).
* Only the inbound SA/policy will be updated as reaction to IP address changes for rekeyed CHILD_SAs that are kept around.
* The parser for strongswan.conf/swanctl.conf now accepts = characters in values without having to put the value in quotes (e.g. for Base64 encoded shared secrets).- Rename strongswan-5.6.2-rpmlintrc to strongswan-rpmlintrc, changing the version string on every version update makes no sense.
* Tue Apr 17 2018 bjorn.lieAATTgmail.com- Update to version 5.6.2:
* Fixed a DoS vulnerability in the parser for PKCS#1 RSASSA-PSS signatures that was caused by insufficient input validation. One of the configurable parameters in algorithm identifier structures for RSASSA-PSS signatures is the mask generation function (MGF). Only MGF1 is currently specified for this purpose. However, this in turn takes itself a parameter that specifies the underlying hash function. strongSwan\'s parser did not correctly handle the case of this parameter being absent, causing an undefined data read. This vulnerability has been registered as CVE-2018-6459.
* When rekeying IKEv2 IKE_SAs the previously negotiated DH group will be reused, instead of using the first configured group, which avoids an additional exchange if the peer previously selected a different DH group via INVALID_KE_PAYLOAD notify. The same is also done when rekeying CHILD_SAs except for the first rekeying of the CHILD_SA that was created with the IKE_SA, where no DH group was negotiated yet. Also, the selected DH group is moved to the front in all sent proposals that contain it and all proposals that don\'t are moved to the back in order to convey the preference for this group to the peer.
* Handling of MOBIKE task queuing has been improved. In particular, the response to an address update (with NAT-D payloads) is not ignored anymore if only an address list update or DPD is queued as that could prevent updating the UDP encapsulation in the kernel.
* On Linux, roam events may optionally be triggered by changes to the routing rules, which can be useful if routing rules (instead of e.g. route metrics) are used to switch from one to another interface (i.e. from one to another routing table). Since routing rules are currently not evaluated when doing route lookups this is only useful if the kernel-based route lookup is used (4664992f7d).
* The fallback drop policies installed to avoid traffic leaks when replacing addresses in installed policies are now replaced by temporary drop policies, which also prevent acquires because we currently delete and reinstall IPsec SAs to update their addresses (35ef1b032d).
* Access X.509 certificates held in non-volatile storage of a TPM 2.0 referenced via the NV index.
* Adding the --keyid parameter to pki --print allows to print private keys or certificates stored in a smartcard or a TPM 2.0.
* Fixed proposal selection if a peer incorrectly sends DH groups in the ESP proposal during IKE_AUTH and also if a DH group is configured in the local ESP proposal and charon.prefer_configured_proposals is disabled (d058fd3c32).
* The lookup for PSK secrets for IKEv1 has been improved for certain scenarios (see #2497 for details).
* MSKs received via RADIUS are now padded to 64 bytes to avoid compatibility issues with EAP-MSCHAPv2 and PRFs that have a block size < 64 bytes (e.g. AES-XCBC-PRF-128, see 73cbce6013).
* The tpm_extendpcr command line tool extends a digest into a TPM PCR.
* Ported the NetworkManager backend from the deprecated libnm-glib to libnm.
* The save-keys debugging/development plugin saves IKE and/or ESP keys to files compatible with Wireshark.- Following upstreams port, replace NetworkManager-devel with pkgconfig(libnm) BuildRequires.- Refresh patches with quilt.- Disable strongswan_fipsfilter.patch, needs rebase or dropping, the file it patches no longer exists in tarball.
* Fri Mar 16 2018 mmnelemaneAATTsuse.com- Removed unused requires and macro calls(bsc#1083261)
* Tue Oct 17 2017 jengelhAATTinai.de- Update summaries and descriptions. Trim filler words and author list.- Drop %if..%endif guards that are idempotent and do not affect the build result.- Replace old $RPM_ shell variables.
* Tue Sep 05 2017 ndasAATTsuse.de- Updated to strongSwan 5.6.0 providing the following changes:
* Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient input validation when verifying RSA signatures, which requires decryption with the operation m^e mod n, where m is the signature, and e and n are the exponent and modulus of the public key. The value m is an integer between 0 and n-1, however, the gmp plugin did not verify this. So if m equals n the calculation results in 0, in which case mpz_export() returns NULL. This result wasn\'t handled properly causing a null-pointer dereference. This vulnerability has been registered as CVE-2017-11185. (bsc#1051222)
* New SWIMA IMC/IMV pair implements the draft-ietf-sacm-nea-swima-patnc Internet Draft and has been demonstrated at the IETF 99 Prague Hackathon.
* The IMV database template has been adapted to achieve full compliance with the ISO 19770-2:2015 SWID tag standard.
* The pt-tls-client can attach and use TPM 2.0 protected private keys via the --keyid parameter.
* By default the /etc/swanctl/conf.d directory is created and
*.conf files in it are included in the default swanctl.conf file.
* The curl plugin now follows HTTP redirects (configurable via strongswan.conf).
* The CHILD_SA rekeying was fixed in charon-tkm and the behavior is refined a bit more since 5.5.3
* libtpmtss supports Intel\'s TSS2 Architecture Broker and Resource Manager interface (tcti-tabrmd).
* more on https://wiki.strongswan.org/versions/66
* Tue Sep 05 2017 ndasAATTsuse.de- fix \"uintptr_t’ undeclared\" compilation error. [+0006-fix-compilation-error-by-adding-stdint.h.patch]
* Mon Jul 31 2017 ndasAATTsuse.de- Updated to strongSwan 5.3.5(bsc#1050691) providing the following changes:
* Fixed a DoS vulnerability in the gmp plugin that was caused by insufficient input validation when verifying RSA signatures. More specifically, mpz_powm_sec() has two requirements regarding the passed exponent and modulus that the plugin did not enforce, if these are not met the calculation will result in a floating point exception that crashes the whole process. This vulnerability has been registered as CVE-2017-9022. Please refer to our blog for details.
* Fixed a DoS vulnerability in the x509 plugin that was caused because the ASN.1 parser didn\'t handle ASN.1 CHOICE types properly, which could result in an infinite loop when parsing X.509 extensions that use such types. This vulnerability has been registered as CVE-2017-9023. Please refer to our blog for details.
* The behavior during IKEv2 CHILD_SA rekeying has been changed in order to avoid traffic loss. When responding to a CREATE_CHILD_SA request to rekey a CHILD_SA the responder already has everything available to install and use the new CHILD_SA. However, this could lead to lost traffic as the initiator won\'t be able to process inbound packets until it processed the CREATE_CHILD_SA response and updated the inbound SA. To avoid this the responder now only installs the new inbound SA and delays installing the outbound SA until it receives the DELETE for the replaced CHILD_SA.
* The messages transporting these DELETEs could reach the peer before packets sent with the deleted outbound SAs reach it. To reduce the chance of traffic loss due to this the inbound SA of the replaced CHILD_SA is not removed for a configurable amount of seconds (charon.delete_rekeyed_delay) after the DELETE has been processed.
* The code base has been ported to Apple\'s ARM64 iOS platform, which required several changes regarding the use of variadic functions. This was necessary because the calling conventions for variadic and regular functions are different there. This means that assigning a non-variadic function to a variadic function pointer, as we did with our enumerator_t::enumerate() implementations and several callbacks, will result in crashes as the called function accesses the arguments differently than the caller provided them. To avoid this issue the enumerator_t interface has been changed and the signature of the callback functions for enumerator_create_filter() and two methods on linked_list_t have been changed. Refer to the developer notes below for details.
* Adds support for fuzzing the certificate parser provided by the default plugins (x509, pem, gmp etc.) on Google\'s OSS-Fuzz infrastructure (or generally with libFuzzer). Several issues found while fuzzing these plugins were fixed.
* Two new options have been added to charon\'s retransmission settings: retransmit_limit and retransmit_jitter. The former adds an upper limit to the calculated retransmission timeout, the latter randomly reduces it. Refer to Retransmission for details.
* A bug in swanctl\'s --load-creds command was fixed that caused unencrypted private keys to get unloaded if the command was called multiple times. The load-key VICI command now returns the key ID of the loaded key on success.
* The credential manager now enumerates local credential sets before global ones. This means certificates supplied by the peer will now be preferred over certificates with the same identity that may be locally stored (e.g. in the certificate cache).
* Adds support for hardware offload of IPsec SAs as introduced by Linux 4.11 for specific hardware that supports this.
* The pki tool loads the curve25519 plugin by default. [- 0006-Make-sure-the-modulus-is-odd-and-the-exponent-not-zero.patch, - 0007-asn1-parser-Fix-CHOICE-parsing.patch]- libhydra is removed as all kernel plugins moved to libcharon
* Tue May 23 2017 ndasAATTsuse.de- Applied patch for \"Don\'t retransmit Aggressive Mode response\" bsc#985012.- Applied upstream patch for \"Insufficient Input Validation in gmp Plugin\" bsc#1039514(CVE-2017-9022).- Applied upstream patch for \"Incorrect x509 ASN.1 parser error handling\" bsc#1039515(CVE-2017-9023). [+0005-ikev1-Don-t-retransmit-Aggressive-Mode-response.patch, +0006-Make-sure-the-modulus-is-odd-and-the-exponent-not-zero.patch, +0007-asn1-parser-Fix-CHOICE-parsing.patch]
* Mon Jul 04 2016 dougAATTuq.edu.au- Updated to strongSwan 5.3.5 providing the following changes: Changes in version 5.3.5:
* Properly handle potential EINTR errors in sigwaitinfo(2) calls that replaced sigwait(3) calls with 5.3.4.
* RADIUS retransmission timeouts are now configurable, courtesy of Thom Troy. Changes in version 5.3.4:
* Fixed an authentication bypass vulnerability in the eap-mschapv2 plugin that was caused by insufficient verification of the internal state when handling MSCHAPv2 Success messages received by the client. This vulnerability has been registered as CVE-2015-8023.
* The sha3 plugin implements the SHA3 Keccak-F1600 hash algorithm family. Within the strongSwan framework SHA3 is currently used for BLISS signatures only because the OIDs for other signature algorithms haven\'t been defined yet. Also the use of SHA3 for IKEv2 has not been standardized yet. Changes in version 5.3.3:
* Added support for the ChaCha20/Poly1305 AEAD cipher specified in RFC 7539 and RFC 7634 using the chacha20poly1305 ike/esp proposal keyword. The new chapoly plugin implements the cipher, if possible SSE-accelerated on x86/x64 architectures. It is usable both in IKEv2 and the strongSwan libipsec ESP backend. On Linux 4.2 or newer the kernel-netlink plugin can configure the cipher for ESP SAs.
* The vici interface now supports the configuration of auxiliary certification authority information as CRL and OCSP URIs.
* In the bliss plugin the c_indices derivation using a SHA-512 based random oracle has been fixed, generalized and standardized by employing the MGF1 mask generation function with SHA-512. As a consequence BLISS signatures unsing the improved oracle are not compatible with the earlier implementation.
* Support for auto=route with right=%any for transport mode connections has been added (the ikev2/trap-any scenario provides examples).
* The starter daemon does not flush IPsec policies and SAs anymore when it is stopped. Already existing duplicate policies are now overwritten by the IKE daemon when it installs its policies.
* Init limits (like charon.init_limit_half_open) can now optionally be enforced when initiating SAs via VICI. For this, IKE_SAs initiated by the daemon are now also counted as half open SAs, which, as a side-effect, fixes the status output while connecting (e.g. in ipsec status).
* Symmetric configuration of EAP methods in left|rightauth is now possible when mutual EAP-only authentication is used (previously, the client had to configure rightauth=eap or rightauth=any, which prevented it from using this same config as responder).
* The initiator flag in the IKEv2 header is compared again (wasn\'t the case since 5.0.0) and packets that have the flag set incorrectly are again ignored.
* Implemented a demo Hardcopy Device IMC/IMV pair based on the \"Hardcopy Device Health Assessment Trusted Network Connect Binding\" (HCD-TNC) document drafted by the IEEE Printer Working Group (PWG).
* Fixed IF-M segmentation which failed in the presence of multiple small attributes in front of a huge attribute to be segmented. Changes in version 5.3.2:
* Fixed a vulnerability that allowed rogue servers with a valid certificate accepted by the client to trick it into disclosing its username and even password (if the client accepts EAP-GTC). This was caused because constraints against the responder\'s authentication were enforced too late. This vulnerability has been registered as CVE-2015-4171. Changes in version 5.3.1:
* Fixed a denial-of-service and potential remote code execution vulnerability triggered by IKEv1/IKEv2 messages that contain payloads for the respective other IKE version. Such payload are treated specially since 5.2.2 but because they were still identified by their original payload type they were used as such in some places causing invalid function pointer dereferences. The vulnerability has been registered as CVE-2015-3991.
* The new aesni plugin provides CBC, CTR, XCBC, CMAC, CCM and GCM crypto primitives for AES-128/192/256. The plugin requires AES-NI and PCLMULQDQ instructions and works on both x86 and x64 architectures. It provides superior crypto performance in userland without any external libraries. Changes in version 5.3.0:
* Added support for IKEv2 make-before-break reauthentication. By using a global CHILD_SA reqid allocation mechanism, charon supports overlapping CHILD_SAs. This allows the use of make-before-break instead of the previously supported break-before-make reauthentication, avoiding connectivity gaps during that procedure. As the new mechanism may fail with peers not supporting it (such as any previous strongSwan release) it must be explicitly enabled using the charon.make_before_break strongswan.conf option.
* Support for \"Signature Authentication in IKEv2\" (RFC 7427) has been added. This allows the use of stronger hash algorithms for public key authentication. By default, signature schemes are chosen based on the strength of the signature key, but specific hash algorithms may be configured in leftauth.
* Key types and hash algorithms specified in rightauth are now also checked against IKEv2 signature schemes. If such constraints are used for certificate chain validation in existing configurations, in particular with peers that don\'t support RFC 7427, it may be necessary to disable this feature with the charon.signature_authentication_constraints setting, because the signature scheme used in classic IKEv2 public key authentication may not be strong enough.
* The new connmark plugin allows a host to bind conntrack flows to a specific CHILD_SA by applying and restoring the SA mark to conntrack entries. This allows a peer to handle multiple transport mode connections coming over the same NAT device for client-initiated flows. A common use case is to protect L2TP/IPsec, as supported by some systems.
* The forecast plugin can forward broadcast and multicast messages between connected clients and a LAN. For CHILD_SA using unique marks, it sets up the required Netfilter rules and uses a multicast/broadcast listener that forwards such messages to all connected clients. This plugin is designed for Windows 7 IKEv2 clients, which announces its services over the tunnel if the negotiated IPsec policy allows it.
* For the vici plugin a Python Egg has been added to allow Python applications to control or monitor the IKE daemon using the VICI interface, similar to the existing ruby gem. The Python library has been contributed by Björn Schuberg.
* EAP server methods now can fulfill public key constraints, such as rightcert or rightca. Additionally, public key and signature constraints can be specified for EAP methods in the rightauth keyword. Currently the EAP-TLS and EAP-TTLS methods provide verification details to constraints checking.
* Upgrade of the BLISS post-quantum signature algorithm to the improved BLISS-B variant. Can be used in conjunction with the SHA256, SHA384 and SHA512 hash algorithms with SHA512 being the default.
* The IF-IMV 1.4 interface now makes the IP address of the TNC access requestor as seen by the TNC server available to all IMVs. This information can be forwarded to policy enforcement points (e.g. firewalls or routers).
* The new mutual tnccs-20 plugin parameter activates mutual TNC measurements in PB-TNC half-duplex mode between two endpoints over either a PT-EAP or PT-TLS transport medium.- Adjusted file lists and removed obsolete patches [- 0005-strongswan-5.2.2-5.3.0_unknown_payload.patch, - 0006-strongswan-5.1.0-5.3.1_enforce_remote_auth.patch, - 0007-strongswan-4.4.0-5.3.3_eap_mschapv2_state.patch]
* Fri Nov 13 2015 mtAATTsuse.de- Applied upstream fix for a authentication bypass vulnerability in the eap-mschapv2 plugin (CVE-2015-8023,bsc#953817). [+ 0007-strongswan-4.4.0-5.3.3_eap_mschapv2_state.patch]
* Thu Jun 04 2015 mtAATTsuse.de- Applied upstream fix for a rogue servers vulnerability, that may enable rogue servers able to authenticate itself with certificate issued by any CA the client trusts, to gain user credentials from a client in certain IKEv2 setups (bsc#933591,CVE-2015-4171). [+ 0006-strongswan-5.1.0-5.3.1_enforce_remote_auth.patch]- Fix to apply unknown_payload patch if fips is disabled (<= 13.1) and renamed it to use number prefix corresponding with patch nr. [- strongswan-5.2.2-5.3.0_unknown_payload.patch, + 0005-strongswan-5.2.2-5.3.0_unknown_payload.patch]
* Mon Jun 01 2015 mtAATTsuse.de- Applied upstream fix for a DoS and potential remote code execution vulnerability through payload type (bsc#931272,CVE-2015-3991) [+ strongswan-5.2.2-5.3.0_unknown_payload.patch]
* Mon Jan 05 2015 mtAATTsuse.de- Updated to strongSwan 5.2.2 providing the following changes: Changes in version 5.2.2:
* Fixed a denial-of-service vulnerability triggered by an IKEv2 Key Exchange payload that contains the Diffie-Hellman group 1025. This identifier was used internally for DH groups with custom generator and prime. Because these arguments are missing when creating DH objects based on the KE payload an invalid pointer dereference occurred. This allowed an attacker to crash the IKE daemon with a single IKE_SA_INIT message containing such a KE payload. The vulnerability has been registered as CVE-2014-9221.
* The left/rightid options in ipsec.conf, or any other identity in strongSwan, now accept prefixes to enforce an explicit type, such as email: or fqdn:. Note that no conversion is done for the remaining string, refer to ipsec.conf(5) for details.
* The post-quantum Bimodal Lattice Signature Scheme (BLISS) can be used as an IKEv2 public key authentication method. The pki tool offers full support for the generation of BLISS key pairs and certificates.
* Fixed mapping of integrity algorithms negotiated for AH via IKEv1. This could cause interoperability issues when connecting to older versions of charon. Changes in version 5.2.1:
* The new charon-systemd IKE daemon implements an IKE daemon tailored for use with systemd. It avoids the dependency on ipsec starter and uses swanctl as configuration backend, building a simple and lightweight solution. It supports native systemd journal logging.
* Support for IKEv2 fragmentation as per RFC 7383 has been added. Like IKEv1 fragmentation it can be enabled by setting fragmentation=yes in ipsec.conf.
* Support of the TCG TNC IF-M Attribute Segmentation specification proposal. All attributes can be segmented. Additionally TCG/SWID Tag, TCG/SWID Tag ID and IETF/Installed Packages attributes can be processed incrementally on a per segment basis.
* The new ext-auth plugin calls an external script to implement custom IKE_SA authorization logic, courtesy of Vyronas Tsingaras.
* For the vici plugin a ruby gem has been added to allow ruby applications to control or monitor the IKE daemon. The vici documentation has been updated to include a description of the available operations and some simple examples using both the libvici C interface and the ruby gem. Changes in version 5.2.0:
* strongSwan has been ported to the Windows platform. Using a MinGW toolchain, many parts of the strongSwan codebase run natively on Windows 7 / 2008 R2 and newer releases. charon-svc implements a Windows IKE service based on libcharon, the kernel-iph and kernel-wfp plugins act as networking and IPsec backend on the Windows platform. socket-win provides a native IKE socket implementation, while winhttp fetches CRL and OCSP information using the WinHTTP API.
* The new vici plugin provides a Versatile IKE Configuration Interface for charon. Using the stable IPC interface, external applications can configure, control and monitor the IKE daemon. Instead of scripting the ipsec tool and generating ipsec.conf, third party applications can use the new interface for more control and better reliability.
* Built upon the libvici client library, swanctl implements the first user of the VICI interface. Together with a swanctl.conf configuration file, connections can be defined, loaded and managed. swanctl provides a portable, complete IKE configuration and control interface for the command line. The first six swanctl example scenarios have been added.
* The SWID IMV implements a JSON-based REST API which allows the exchange of SWID tags and Software IDs with the strongTNC policy manager.
* The SWID IMC can extract all installed packages from the dpkg (Debian, Ubuntu, Linux Mint etc.), rpm (Fedora, RedHat, OpenSUSE, etc.), or pacman (Arch Linux, Manjaro, etc.) package managers, respectively, using the swidGenerator (https://github.com/strongswan/swidGenerator) which generates SWID tags according to the new ISO/IEC 19770-2:2014 standard.
* All IMVs now share the access requestor ID, device ID and product info of an access requestor via a common imv_session object.
* The Attestation IMC/IMV pair supports the IMA-NG measurement format introduced with the Linux 3.13 kernel.
* The aikgen tool generates an Attestation Identity Key bound to a TPM.
* Implemented the PT-EAP transport protocol (RFC 7171) for Trusted Network Connect.
* The ipsec.conf replay_window option defines connection specific IPsec replay windows. Original patch courtesy of Zheng Zhong and Christophe Gouault from 6Wind.- Adjusted file lists and removed obsolete patches [- 0005-restore-registration-algorithm-order.bug897512.patch, - 0006-strongswan-5.1.2-5.2.1_modp_custom.CVE-2014-9221.patch]- Adopted/Merged fipscheck patches [
* strongswan_fipscheck.patch, strongswan_fipsfilter.patch]
* Wed Dec 17 2014 mtAATTsuse.de- Disallow brainpool elliptic curve groups in fips mode (bnc#856322). [
* strongswan_fipsfilter.patch]
* Thu Dec 11 2014 mtAATTsuse.de- Applied an upstream fix for a denial-of-service vulnerability, which can be triggered by an IKEv2 Key Exchange payload, that contains the Diffie-Hellman group 1025 (bsc#910491,CVE-2014-9221). [+ 0006-strongswan-5.1.2-5.2.1_modp_custom.CVE-2014-9221.patch]- Adjusted whilelist of approved algorithms in fips mode (bsc#856322). [
* strongswan_fipsfilter.patch]- Renamed patch file to match it\'s patch number: [- 0001-restore-registration-algorithm-order.bug897512.patch, + 0005-restore-registration-algorithm-order.bug897512.patch]
* Tue Nov 25 2014 mtAATTsuse.de- Updated strongswan-hmac package description (bsc#856322).
* Fri Nov 21 2014 mtAATTsuse.de- Disabled explicit gpg validation; osc source_validator does it.- Guarded fipscheck and hmac package in the spec file for >13.1.
* Thu Nov 20 2014 mtAATTsuse.de- Added generation of fips hmac hash files using fipshmac utility and a _fipscheck script to verify binaries/libraries/plugings shipped in the strongswan-hmac package. With enabled fips in the kernel, the ipsec script will call it before any action or in a enforced/manual \"ipsec _fipscheck\" call. Added config file to load openssl and kernel af-alg plugins, but not all the other modules which provide further/alternative algs. Applied a filter disallowing non-approved algorithms in fips mode. (fate#316931,bnc#856322). [+ strongswan_fipscheck.patch, strongswan_fipsfilter.patch]- Fixed file list in the optional (disabled) strongswan-test package.- Fixed build of the strongswan built-in integrity checksum library and enabled building it only on architectures tested to work.- Fix to use bug number 897048 instead 856322 in last changes entry.- Applied an upstream patch reverting to store algorithms in the registration order again as ordering them by identifier caused weaker algorithms to be proposed first by default (bsc#897512). [+0001-restore-registration-algorithm-order.bug897512.patch]