From: "The IPFire Project." <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: [IPFire Announcement] IPFire 2.11 - Core Update 59 released
Date: Fri, 18 May 2012 16:05:55 +0200 [thread overview]
Message-ID: <mailman.98.1337349983.1002.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
The last Core Update has just been a week old, but it is now time for
the next one.
This is to announce the release of Core Update 59, which comes with a
lot of security fixes. Hence we recommend to update as soon as possible.
Security fixes:
openssl (0.9.8x) – which mainly fixes a DoS issue: CVE-2012-2333
php (5.3.13) – Fixes CVE-2012-2311. It was possible to add additionional
parameters to a CGI call.
python (2.7.3) – which mainly fixes the hash table collision bug that
has been around for some time. It also contains a lot of minor bugfixes
for the language itself.
More updates:
The openssh server has been updates to version 6.0p1.
strongswan has been updated to 4.6.3, which is a minor bugfix release.
IPFire does not allow to set the MTU to 576 on RED. There are some cable
modems around which a broken DHCP server that sets the MTU to 576.
However, this causes a huge slowdown of the internet connection which
does no longer exists anymore.
Sorry for bothering with two updates this week, but as you can see, the
world is spining and we rather like to fix problems than waiting for
exploits showing up. If you appreciate this, please donate.
http://www.ipfire.org/donation
reply other threads:[~2012-05-18 14:05 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.98.1337349983.1002.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