From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-core@lists.openembedded.org
Subject: [PATCH 00/13] Pull request jethro-next
Date: Thu, 17 Nov 2016 19:24:48 -0800 [thread overview]
Message-ID: <cover.1479396619.git.akuster808@gmail.com> (raw)
Please consider these for jethro-next
The following changes since commit 820b835e3cbfefb1ed11faca95a67ef6f5475fb1:
dev-manual: Fixed typo for "${INC_PR}.0" (2016-11-16 10:38:29 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akuster/jethro-next
http://git.yoctoproject.org/cgit.cgi//log/?h=akuster/jethro-next
Armin Kuster (13):
gnutils: Security fix CVE-2016-7444
bind: Security fix CVE-2016-2775
bind: Security fix CVE-2016-2776
openssl: Security fix CVE-2016-2179
openssl: Security fix CVE-2016-8610
python-2.7: Security fix CVE-2016-0772
python-2.7: Security fix CVE-2016-5636
python-2.7: Security fix CVE-2016-5699
python-2.7: Security fix CVE-2016-1000110
tzcode-native: update to 2016h
tzdata: Update to 2016h
tzcode: update to 2016i
tzdata: update to 2016i
.../bind/bind/CVE-2016-2775.patch | 84 +++++++
.../bind/bind/CVE-2016-2776.patch | 112 +++++++++
meta/recipes-connectivity/bind/bind_9.10.2-P4.bb | 2 +
.../openssl/openssl/CVE-2016-2179.patch | 255 +++++++++++++++++++++
.../openssl/openssl/CVE-2016-8610.patch | 124 ++++++++++
.../recipes-connectivity/openssl/openssl_1.0.2h.bb | 2 +
.../python/python/CVE-2016-0772.patch | 42 ++++
.../python/python/CVE-2016-1000110.patch | 145 ++++++++++++
.../python/python/CVE-2016-5636.patch | 42 ++++
.../python/python/CVE-2016-5699.patch | 162 +++++++++++++
meta/recipes-devtools/python/python_2.7.9.bb | 4 +
...code-native_2016g.bb => tzcode-native_2016i.bb} | 8 +-
.../tzdata/{tzdata_2016g.bb => tzdata_2016i.bb} | 4 +-
.../gnutls/gnutls/CVE-2016-7444.patch | 31 +++
meta/recipes-support/gnutls/gnutls_3.3.17.1.bb | 1 +
15 files changed, 1012 insertions(+), 6 deletions(-)
create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2016-2775.patch
create mode 100644 meta/recipes-connectivity/bind/bind/CVE-2016-2776.patch
create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-2179.patch
create mode 100644 meta/recipes-connectivity/openssl/openssl/CVE-2016-8610.patch
create mode 100644 meta/recipes-devtools/python/python/CVE-2016-0772.patch
create mode 100644 meta/recipes-devtools/python/python/CVE-2016-1000110.patch
create mode 100644 meta/recipes-devtools/python/python/CVE-2016-5636.patch
create mode 100644 meta/recipes-devtools/python/python/CVE-2016-5699.patch
rename meta/recipes-extended/tzcode/{tzcode-native_2016g.bb => tzcode-native_2016i.bb} (68%)
rename meta/recipes-extended/tzdata/{tzdata_2016g.bb => tzdata_2016i.bb} (98%)
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2016-7444.patch
--
2.3.5
reply other threads:[~2016-11-18 3:25 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.1479396619.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.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.