From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: development@lists.ipfire.org
Subject: IPFire 2.19 - Core Update 102 released
Date: Wed, 04 May 2016 21:57:02 +0200 [thread overview]
Message-ID: <0MWiwF-1b8jHm3pRz-00XvY1@mrelayeu.kundenserver.de> (raw)
In-Reply-To: <mailman.495.1462391938.1659.ipfire-announce@lists.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
h_t_t_p://www.ipfire.org/news/ipfire-2-19-core-update-102-released
This is the official release announcement for IPFire 2.19 – Core Update 102.
This update contains various security fixes in the OpenSSL library. It is
recommended to install this update as soon as possible.
OpenSSL Security Fixes
The OpenSSL team published fixes for several security issues [1] yesterday:
* Memory corruption in the ASN.1 encoder (CVE-2016-2108)
* Padding oracle in AES-NI CBC MAC check (CVE-2016-2107)
* EVP_EncodeUpdate overflow (CVE-2016-2105)
* EVP_EncryptUpdate overflow (CVE-2016-2106)
* ASN.1 BIO excessive memory allocation (CVE-2016-2109)
* EBCDIC overread (CVE-2016-2176)
This Core Update brings you OpenSSL 1.0.2h which fixes all of these above.
Additionally OpenSSH is updated to version 7.2p2 and will be restarted during
the update.
We are currently crowdfunding a Captive Portal for IPFire [2] and would like you
to ask to check it out and support us!
Please help us to support the work on IPFire Project with your donation [3].
[1] h_t_t_ps://www.openssl.org/news/secadv/20160503.txt
[2] h_t_t_p://wishlist.ipfire.org/wish/the-ipfire-captive-portal
[3] h_t_t_p://www.ipfire.org/donate
_______________________________________________
IPFire-Announce mailing list
IPFire-Announce(a)lists.ipfire.org
h_t_t_p://lists.ipfire.org/mailman/listinfo/ipfire-announce
next parent reply other threads:[~2016-05-04 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.495.1462391938.1659.ipfire-announce@lists.ipfire.org>
2016-05-04 19:57 ` The IPFire Project [this message]
2016-05-04 19:57 Michael Tremer
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=0MWiwF-1b8jHm3pRz-00XvY1@mrelayeu.kundenserver.de \
--to=ipfire-announce@lists.ipfire.org \
--cc=development@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