From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.15 - Core Update 85 released
Date: Sun, 19 Oct 2014 18:03:45 +0200 [thread overview]
Message-ID: <mailman.357.1413734655.23993.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
http://www.ipfire.org/news/ipfire-2-15-core-update-85-released
This is the official release announcement for IPFire 2.15 – Core Update
85. It comes with security fixes for the SSL issue known as POODLE,
which was recently discovered.
POODLE (CVE-2014-3566)
As there is no fix for POODLE, the OpenSSL developers applied a
workaround called “Signaling Cipher Suite Value” (SCSV) that prevents
protocol downgrade attacks (the downgrade dance) on the TLS protocol.
More information about this mechanism can be found in the IETF draft [1]
and more about POODLE can be found in the POODLE whitepaper [2].
As a precaution we disabled SSL 3.0 for the web administration
interface. Accessing that will require you to use a recent browser and
operating system that is able to use TLS 1.0 or a more recent version.
We already made some experiences with this as our web and mail servers
do not allow to use SSL 3.0 since a couple of weeks and there were
absolutely no reports from people who are not able to access our
websites.
We recommend to install this update as soon as possible. After doing so,
your system will need to reboot.
Please support the IPFire project with your donation [3]. Your help is a
foundation of this project and very much appreciated by all
contributors.
[1] https://tools.ietf.org/html/draft-ietf-tls-downgrade-scsv-00
[2] https://www.openssl.org/~bodo/ssl-poodle.pdf
[3] http://www.ipfire.org/donate
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2014-10-19 16:03 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.357.1413734655.23993.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