From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [jethro][PATCH 0/2] Consolidated security pull request
Date: Thu, 3 Mar 2016 10:32:38 +0000 [thread overview]
Message-ID: <cover.1457001019.git.joshua.g.lock@intel.com> (raw)
This pull request picks up a couple of outstanding Jethro security fixes which
are also required for the fido branch. Note: the wpa-supplicant change isn't
required for master and an equivelant openssl fix is queued for master.
Please consider them for merging.
Regards,
Joshua
The following changes since commit 0c702756dd0009c4112028fbf2479a346867b32c:
build-appliance-image: Update to jethro head revision (2016-02-24 09:04:05 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib joshuagl/jethro
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/jethro
Armin Kuster (1):
openssl: Security fix CVE-2016-0800
Hongxu Jia (1):
wpa-supplicant: Fix CVE-2015-8041
.../openssl/openssl/CVE-2016-0800.patch | 198 +++++++
.../openssl/openssl/CVE-2016-0800_2.patch | 592 +++++++++++++++++++++
.../openssl/openssl/CVE-2016-0800_3.patch | 503 +++++++++++++++++
.../recipes-connectivity/openssl/openssl_1.0.2d.bb | 3 +
...load-length-validation-in-NDEF-record-par.patch | 64 +++
.../wpa-supplicant/wpa-supplicant_2.4.bb | 1 +
6 files changed, 1361 insertions(+)
create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-0800.patch
create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-0800_2.patch
create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-0800_3.patch
create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/0001-NFC-Fix-payload-length-validation-in-NDEF-record-par.patch
--
2.5.0
reply other threads:[~2016-03-03 10:33 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=cover.1457001019.git.joshua.g.lock@intel.com \
--to=joshua.g.lock@intel.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.