From: "The IPFire Project." <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: [IPFire Announcement] IPFire 2.11 - Core Update 57
Date: Wed, 07 Mar 2012 17:18:17 +0100 [thread overview]
Message-ID: <mailman.172.1331137132.1138.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Today, we are releasing Core Update 57 for IPFire 2.11. It is again a
minor bugfix and security update.
Software updates
These components have been updated to address various security issues or
potential DDoS attacks:
php: security update to 5.3.10
apache: security update to 2.2.22
squid: update to 3.19
Misc. changes
A bug in the GUI of the outgoing firewall was fixed, which automatically
disabled a rule after it has been edited (#10022
https://bugzilla.ipfire.org/show_bug.cgi?id=10022 ).
vim does now work better on remote consoles like PuTTY. Thanks for
patches to Mathias Schneuwly (#10021
https://bugzilla.ipfire.org/show_bug.cgi?id=10021 ).
The welcome banner that is shown to Cisco’s roadwarrior VPN client is
now customized and says “Welcome to IPFire – An Open Source Firewall
Solution”.
Recently updated addons
These addons have been updated in the last few weeks:
cups: update to version 1.4.8
nut: update to latest version 2.6.3
pound: update to latest stable 2.6
If you like, you may express your appreciation for these updates by
making a donation to support the IPFire Project.
http://www.ipfire.org/donation
Thanks to all who have contributed to this core update. The full
changelog can be reviewed on gitweb.
http://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=refs/heads/core57
reply other threads:[~2012-03-07 16:18 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.172.1331137132.1138.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