From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.17 - Core Update 97 released
Date: Fri, 29 Jan 2016 17:50:12 +0000 [thread overview]
Message-ID: <mailman.128.1454089908.1532.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
http://www.ipfire.org/news/ipfire-2-17-core-update-97-released
This is the official release announcement for IPFire 2.17 – Core Update
97. An other OpenSSL security fix has been released, which is shipped
in this Core Update among some other security vulnerabilities. As this
is a rather urgent update, we recommend to install it as soon as
possible. We also recommend rebooting after the update has been
installed.
OpenSSL security fixes – 1.0.2f
It is possible to exploit the Diffie-Hellman key exchange (CVE-2016-
0701, [1])and get hold of the server’s private exponent. With that any
future connections can be decrypted. Please check out the original
security advisory for more details.
A second fix (CVE-2015-3197) in the OpenSSL library fixes the
deactivation of some SSLv2 ciphers.
An other change will strengthen SSL connections against being taken
over by a man-in-the-middle attack that tries to downgrade the length
of the Diffie-Hellman key that is being used.
OpenSSH 7.1p2
An information leak (CVE-2016-0777) flaw was found in the way the
OpenSSH client roaming feature was implemented. A malicious server
could potentially use this flaw to leak portions of memory (possibly
including private SSH keys) of a successfully authenticated OpenSSH
client.
The SSH daemon will be restarted during the update in case it is
enabled.
Please help us to sustain the work on IPFire Project
with your donation [2].
[1] http://openssl.org/news/secadv/20160128.txt
[2] http://www.ipfire.org/donate
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-01-29 17:50 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.128.1454089908.1532.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