From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.17 - Core Update 93 released
Date: Mon, 17 Aug 2015 20:26:02 +0100 [thread overview]
Message-ID: <mailman.81.1439839601.3957.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
http://www.ipfire.org/news/ipfire-2-17-core-update-93-released
This is the official release announcement of IPFire 2.17 – Core Update
93. This update comes with various security fixes in the Squid web
proxy, the dnsmasq DNS proxy server and the Perl-compatible regular
expressions library.
DDNS Client Update
ddns, our dynamic DNS update client, has been updated to version 008.
This version is more robust against network errors on the path and
server errors at the provider. Updates will then be retried frequently.
* The providers joker.com and DNSmadeEasy are now supported
* A crash when updating namecheap records has been fixed
Misc
* Pakfire was fixed and now correctly pulls additional dependencies of
add-on packages when updating from an older version.
* TRIM is disabled on some SSDs with known firmware bugs that cause
data loss.
* squid-accounting: Fix various typos in translations
* /etc/ipsec.user-post.conf is added to the backup if it exists
Updated packages
bind 9.10.2-P3, daq 2.0.6, dnsmasq 2.75, libevent 2.0.22-stable
(moved to the core system from add-on), libpcap 1.7.4, nettle 3.1.1,
pcre (fixes CVE-2015-5073), squid 3.4.14
Add-ons
cups 2.0.4, make 4.1, nano 2.4.2
You can support this project by getting involved into development [1],
writing documentation, support fellow IPFire users or with your
donation [2].
[1] http://www.ipfire.org/getinvolved
[2] http://www.ipfire.org/donate
reply other threads:[~2015-08-17 19:26 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.81.1439839601.3957.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