From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.23 - Core Update 135 released
Date: Wed, 04 Sep 2019 20:10:12 +0100 [thread overview]
Message-ID: <mailman.17.1567624277.759.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
https://blog.ipfire.org/post/ipfire-2-23-core-update-135-released
This is the official release announcement for IPFire 2.23 - Core Update 135, which is packed with a new kernel, various bug fixes and we recommend to install it as soon as possible.
Kernel Update
The IPFire Linux kernel has been rebased on 4.14.138 and various improvements have been added. Most notably, this kernel - once again - fixes CPU vulnerabilities.
Misc.
• On x86_64, the effectiveness of KASLR has been improved which prevents attackers from executing exploits or injecting code
• DNS: unbound has been improved so that it will take much less time to start up in case a DNS server is unavailable.
• Scripts that boot up IPFire have been improved, rewritten and cleaned up for a faster boot and they now handle some error cases better
• Updated packages: dhcpcd 7.2.3, nettle 3.5.1, squid 4.8, tzdata 2019b
Add-ons
Updated Packages
• bird 2.0.4
• clamav 0.101.3
• iperf 2.0.13
• iperf3 3.7
• mc 4.8.23
• pcengines-firmware 4.9.0.7
reply other threads:[~2019-09-04 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.17.1567624277.759.ipfire-announce@lists.ipfire.org \
--to=ipfire-announce@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox