From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.17 - Core Update 99
Date: Sat, 05 Mar 2016 12:31:30 +0000 [thread overview]
Message-ID: <mailman.148.1457181106.1659.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
http://www.ipfire.org/news/ipfire-2-17-core-update-99-released
This is the official release announcement for IPFire 2.17 – Core Update
99. Another OpenSSL security fix has been released, so that we created
this Core Update that fixes that among some other security
vulnerabilities.
OpenSSL security fixes – 1.0.2g
Please check out the original security advisory [1] for more details.
* Cross-protocol attack on TLS using SSLv2 (DROWN) (CVE-2016-0800)
* Double-free in DSA code (CVE-2016-0705)
* Memory leak in SRP database lookups (CVE-2016-0798)
* BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
(CVE-2016-0797)
* Fix memory issues in BIO_*printf functions (CVE-2016-0799)
* Side channel attack on modular exponentiation (CVE-2016-0702)
* Divide-and-conquer session key recovery in SSLv2 (CVE-2016-0703)
* Bleichenbacher oracle in SSLv2 (CVE-2016-0704)
IPFire is most likely not vulnerable by the most famous of all these
vulnerabilities known as DROWN. However we recommend updating as soon
as possible and we also recommend to reboot the system afterwards.
OpenSSH 7.2p1
This is primarily a bugfix release [2].
The SSH daemon will be restarted during the update in case it
is enabled.
We are currently crowdfunding a Captive Portal for IPFire [3] and would
like you to ask to check it out and support us!
Please help us to sustain the work on IPFire Project with your donation
[4].
[1] http://openssl.org/news/secadv/20160301.txt
[2] http://www.openssh.com/txt/release-7.2
[3] http://wishlist.ipfire.org/wish/the-ipfire-captive-portal
[4] http://www.ipfire.org/donate
reply other threads:[~2016-03-05 12:31 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.148.1457181106.1659.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