From: akuster808 <akuster808@gmail.com>
To: "Mittal, AnujX" <anujx.mittal@intel.com>,
Armin Kuster <akuster808@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/9] Jethro pull request
Date: Tue, 27 Sep 2016 08:18:31 -0700 [thread overview]
Message-ID: <6fb04c61-e315-afcd-452e-17b1a91b7b7f@gmail.com> (raw)
In-Reply-To: <DFCB2C9E62139C41B3FDE8F2B46593310A19B928@PGSMSX101.gar.corp.intel.com>
On 09/25/2016 06:05 PM, Mittal, AnujX wrote:
> Hi,
>
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Armin Kuster
>> Sent: Sunday, September 25, 2016 11:05 PM
>> To: akuster@mvista.com; openembedded-core@lists.openembedded.org
>> Subject: [OE-core] [PATCH 0/9] Jethro pull request
>>
>> Please consider these changes for Jethro
>>
>> The following changes since commit
>> c9c85df86cd2270b144fa824ef76adedd3636c8a:
>>
>> util-linux: Security fix for CVE-2016-5011 (2016-09-23 23:21:43 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.openembedded.org/openembedded-core-contrib akuster/jethro-next
>> http://cgit.openembedded.org/cgit.cgi/openembedded-core-
>> contrib/log/?h=akuster/jethro-next
>>
>> Armin Kuster (9):
>> openssl: Security fix CVE-2016-2180
>> openssl: Security fix CVE-2016-8181
>> openssl: Security fix CVE-2016-2182
>> openssl: Security fix CVE-2016-6304
>
> I think there's a typo here. Shouldn't this be CVE-2016-6302?
yep.
I will re-spin shortly.
thank,
Armin
>
>> openssl: Security fix CVE-2016-6303
>> openssl: Security fix CVE-2016-6304
>> openssl: Security fix CVE-2016-6303
>
> And, this CVE-2016-6306?
>
>> tzdata: update to 2016f
>> tzcode-native: update to 2016f
>>
>> .../openssl/openssl/CVE-2016-2180.patch | 44 ++++
>> .../openssl/openssl/CVE-2016-2181_p1.patch | 91 ++++++++
>> .../openssl/openssl/CVE-2016-2181_p2.patch | 239
>> +++++++++++++++++++++
>> .../openssl/openssl/CVE-2016-2181_p3.patch | 30 +++
>> .../openssl/openssl/CVE-2016-2182.patch | 70 ++++++
>> .../openssl/openssl/CVE-2016-6302.patch | 53 +++++
>> .../openssl/openssl/CVE-2016-6303.patch | 36 ++++
>> .../openssl/openssl/CVE-2016-6304.patch | 75 +++++++
>> .../openssl/openssl/CVE-2016-6306.patch | 71 ++++++
>> .../recipes-connectivity/openssl/openssl_1.0.2h.bb | 9 +
>> ...code-native_2016e.bb => tzcode-native_2016f.bb} | 8 +-
>> .../tzdata/{tzdata_2016e.bb => tzdata_2016f.bb} | 4 +-
>> 12 files changed, 724 insertions(+), 6 deletions(-)
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 2180.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 2181_p1.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 2181_p2.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 2181_p3.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 2182.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 6302.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 6303.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 6304.patch
>> create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-
>> 6306.patch
>> rename meta/recipes-extended/tzcode/{tzcode-native_2016e.bb => tzcode-
>> native_2016f.bb} (68%)
>> rename meta/recipes-extended/tzdata/{tzdata_2016e.bb => tzdata_2016f.bb}
>> (98%)
>>
>> --
>> 2.7.4
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2016-09-27 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 15:05 [PATCH 0/9] Jethro pull request Armin Kuster
2016-09-26 1:05 ` Mittal, AnujX
2016-09-27 15:18 ` akuster808 [this message]
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=6fb04c61-e315-afcd-452e-17b1a91b7b7f@gmail.com \
--to=akuster808@gmail.com \
--cc=anujx.mittal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox