From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.19 - Core Update 108 released
Date: Wed, 21 Dec 2016 19:27:09 +0000 [thread overview]
Message-ID: <mailman.85.1482348529.1219.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
http://www.ipfire.org/news/ipfire-2-19-core-update-108-released
Just before Christmas, we are going to release the last Core Update for
2016. IPFire 2.19 – Core Update 108 brings some minor bug fixes and
feature enhancements, some security fixes in ntp and various fixes in
the squid web proxy.
Asynchronous Logging
Asynchronous logging is now enabled by default and not configurable any
more. This made some programs that wrote an extensive amount of log
messages slow down and possible unresponsive over the network which
causes various problems. This was seen on systems with very slow flash
media and virtual environments.
Miscellaneous
* The check that tests DNS servers for any misconfiguration assumed
some name servers being validating although they were not and very
likely not working at all. This has been fixed now and systems using
these broken name servers should fall back to recursor mode.
* A problem in the firewall GUI was fixed that prohibited adding an
IPsec VPN connection and OpenVPN connection with the same name to a
firewall group.
Updated Core Packages
* strongswan was updated to version 5.5.1 which fixes various bugs
* ntp was updated to version 4.2.8p9 which fixes various security
issues
* ddns was updated to version 008
Updated Add-ons
* nano, the text editor, was updated to version 2.7.1
* tor, the anonymity network, was updated to version 0.2.8.10
We are currently crowdfunding a Captive Portal for IPFire and would
like you to ask to check it out and support us [1]!
Please help us to support the work on IPFire Project with your donation
[2].
[1] http://wishlist.ipfire.org/wish/the-ipfire-captive-portal
[2] http://www.ipfire.org/donate
reply other threads:[~2016-12-21 19:27 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.85.1482348529.1219.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