From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.19 - Core Update 107 released
Date: Tue, 08 Nov 2016 19:31:13 +0000 [thread overview]
Message-ID: <mailman.944.1478633517.1498.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
http://www.ipfire.org/news/ipfire-2-19-core-update-107-released
This is the official release announcement for IPFire 2.19 – Core Update 107. It
mainly comes with a fix for the Dirty COW vulnerability in the Linux kernel and
fixes various issues with the latest DNS proxy update in Core Update version
106.
Dirty COW
This update patches the IPFire Linux kernel against a recently disclosed
vulnerability called Dirty COW [1]. This is a local privilege escalation bug
which could be used by a local attacker to gain root privileges.
Misc.
* A further patch fixes Intel processors with AES-NI which’s hardware supports
encryption with 256 and 192 bit key length, but was not properly implemented
in the Linux kernel
* A fix to show the new unbound DNS proxy in the log section of the web user
interface
* hdparm 9.5.0 and libjpeg 1.5.1 have been updated
We are currently crowdfunding a Captive Portal for IPFire [2] and would like you
to ask to check it out and support us!
Please help us to support the work on IPFire Project with your donation [3].
[1] https://en.wikipedia.org/wiki/Dirty_COW
[2] http://wishlist.ipfire.org/wish/the-ipfire-captive-portal
[3] http://www.ipfire.org/donate
reply other threads:[~2016-11-08 19:31 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.944.1478633517.1498.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