https://blog.ipfire.org/post/ipfire-2-21-core-update-130-released
Just a couple of days after the release of IPFire 2.21 - Core Update 130, the next release is available. This is an emergency update with various bug fixes and a large number of security fixes.
Security
IPFire 2.21 - Core Update 130 contains security updates for the following packages:
• Apache 2.4.39: The Apache Web Server, which runs the IPFire Web User Interface, was vulnerable for various privilege escalations (CVE-2019-0211), access control bypasses (CVE-2019-0215, CVE-2019-0217), DoS attacks (CVE-2019-0197), buffer overflow (CVE-2019-0196) and a URL normalisation inconsistency (CVE-2019-0220). They are all regarded to be of "low" severity.
• wget 1.20.3: wget has had multiple vulnerabilities that allowed an attacker to execute arbitrary code (CVE-2019-5953).
• clamav 0.101.2: ClamAV, the virus scanner, has had multiple vulnerabilities that allowed DoS and a buffer overflow in a bundled third-party library.
Although some of these vulnerabilities are only of low severity, we recommend to install this update as soon as possible!
IPsec Regression
The last update introduced a regression in the IPsec stack that caused that the firewall could no longer access any hosts on the remote side when the tunnel was run in tunnel mode without any VTI/GRE interfaces. This update fixes that.
https://blog.ipfire.org/post/ipfire-2-21-core-update-129-released
This is the official release announcement for IPFire 2.21 - Core Update 129 - an update that introduces routed IPsec VPNs and comes with various other changes that update the core system and fix several bugs.
IPsec Reloaded
IPsec has been massively extended. Although IPsec in IPFire is already quite versatile and delivered high performance [1], some features for experts were required and are now available through the web UI:
• Routed VPNs with GRE & VTI [2]
• Transport Mode for net-to-net tunnels
• IPsec connections can now originate from any public IP address of the IPFire installation. This can be selected on a per-connection basis.
The code has also been cleaned up the UI has been made a little bit tidier to accommodate for the new settings.
Smaller changes include:
• The "On-Demand" mode is finally the default setting. Tunnels will shut down when they are not used and they will be established again when they are required.
Misc.
• DHCP: A crash has been fixed when filenames containing a slash have been entered for PXE boot.
• DHCP: Editing static leases has been fixed
• Domains in the "DNS Forwarding" section can now be disabled for DNSSEC validation. This is a dangerous change, but has been requested by many users.
• Updated packages: bind 9.11.6, groff 1.22.4, ipset 7.1, iptables 1.8.2, less 530, libgcrypt 1.8.4, openssl 1.1.1b, openvpn 2.4.7, squid 4.6, tar 1.32, unbound 1.9.0, wpa_supplicant 2.7
• New commands: kdig 2.8.0
• The build system has been optimised to reduce build time of the whole distribution to around 4-5 hours on a fast machine.
Add-Ons
• Alexander Koch has contributed zabbix_agentd which is the agent that is installed on the monitored machine. With this [3], IPFire can now be integrated into an environment that is monitored by Zabbix.
• On that note, the SNMP daemon has also been updated to version 5.8 for people who use the SNMP protocol for monitoring.
• tor has been updated to 0.3.5.8 and some minor bugs have been fixed in the web user interface
• The spectre-meltdown-checker script is available as an add-on which allows IPFire users to test their hardware for vulnerabilities
• Other updates: amavisd 2.11.1, hostapd 2.7, postfix 3.4.3
Thank you very much to everyone who contributed to this Core Update. Please support our project and donate today [4] so that we can keep up our work!
[1] https://blog.ipfire.org/post/feature-spotlight-galois-counter-mode-ipsec-wi…
[2] https://blog.ipfire.org/post/routed-ipsec-vpns-are-landing-in-ipfire-2-21-c…
[3] https://wiki.ipfire.org/addons/zabbix_agentd
[4] https://www.ipfire.org/donate
Hello editors,
this is a pre-announcement email to all editors out there who write about
IPFire. We would like to let you know, that we are planning to release the next
IPFire release, IPFire 2.21 Core Update 129 next Monday, April 8th between 10:00
and 14:00 UTC.
We are sending you this announcement to give you some time to prepare a news
article about this new release of IPFire to help us make IPFire better-known and
of course to make our existing users aware of this exciting new update being
ready to be installed. We are very grateful for your support for our project!
The changelog can be found here:
https://blog.ipfire.org/post/ipfire-2-21-core-update-129-is-ready-for-testi…
In this release brings many extensions to the IPsec stack including support for
GRE/VTI tunnels and transport mode as well as many more smaller changes.
Please get in touch if you have any further questions.
We will send you the final announcement when the update is officially released.
Thank you very much for supporting our project!
Best regards,
-Michael