From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.21 - Core Update 126 released
Date: Fri, 28 Dec 2018 13:16:11 +0000 [thread overview]
Message-ID: <mailman.51.1546003541.1539.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
https://blog.ipfire.org/post/ipfire-2-21-core-update-126-released
Finally, the next release of IPFire is available: IPFire 2.21 - Core Update 126 This update comes with a new kernel and security enhancements. This change log is rather short, but the changes are very important.
Thank you very much to all of you who have supported our Donations Challenge [1] so far. We have received a lot of nice words and support from you, but we are not there, yet! Please support our project and donate!
Linux 4.14.86
The kernel has been updated to the latest version of the Linux 4.14.x branch which brings various improvements around stability, enhances performance and fixes some security vulnerabilities. This kernel also has major updates for the Spectre and Meltdown vulnerabilities that remove previously existent performance penalties in some use-cases.
The kernel's modules are now compressed with the XZ algorithm which will save some space on disk as the kernel is one of the largest components of IPFire.
Misc.
* openssl has been updated to 1.1.0j and 1.0.2q which fixes some minor security issues and has various bug fixes
* The bind package has now changed to ship shared libraries which it did not before. Those allow that commands like dig and host use those shared libraries and are no longer statically linked. This makes the files a lot smaller.
* Stéphane Pautrel has substantially improved the French translation of IPFire. Thank you very much for that!
Add-ons
* Updated packages: bird 2.0.2, nano 3.2
* New packages: shairport-sync
Thanks for the people who contributed to this Core Update. Please support us and donate!
[1] https://blog.ipfire.org/post/donations-challenge
reply other threads:[~2018-12-28 13:16 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.51.1546003541.1539.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