Core 134 Geoip had the same string of geoip boot errors as Core update 133
does. Tried the missing folder fix I found for core update 133 but if fails
on to fix core update 134. So somewhat different problem.
Regards
Wayne
https://blog.ipfire.org/post/ipfire-2-23-core-update-134-released
This is the official release announcement for IPFire 2.23 - Core Update 134. This update ships security fixes in the Linux kernel for the "SACK Panic" attack as well as some other smaller fixes.
SACK Panic (CVE-2019-11477 & CVE-2019-11478)
The Linux kernel was vulnerable for two DoS attacks against its TCP stack. The first one made it possible for a remote attacker to panic the kernel and a second one could trick the system into transmitting very small packets so that a data transfer would have used the whole bandwidth but filled mainly with packet overhead.
The IPFire kernel is now based on Linux 4.14.129, which fixes this vulnerability and fixes various other bugs.
The microcode for some Intel processors has also been updated and includes fixes for some vulnerabilities of the Spectre/Meltdown class for some Intel Xeon processors.
Misc.
• Package updates: bind 9.11.8, unbound 1.9.2, vim 8.1
• The French translation has been updated by Stéphane Pautrel and translates various strings as well as improving some others
• We now prefer other cipher modes over CBC when IPFire itself opens a TLS connection. CBC is now considered to be substantially weaker than GCM.
• Email addresses entered in the web UI can now contain underscores.
• The Captive Portal now comes up properly after IPFire is being rebooted.
