From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-core@lists.openembedded.org
Subject: [PATCH 00/36] Morty-next pull request
Date: Tue, 7 Nov 2017 08:55:13 -0800 [thread overview]
Message-ID: <cover.1510071393.git.akuster@mvista.com> (raw)
From: Armin Kuster <akuster@mvista.com>
Cover letter only
Please consider these changes for morty.
Clean AB build
The following changes since commit 6da3e0a0abf1251db243548639979f8d74e99766:
bitbake: Replace deprecated git branch parameter "--set-upstream" (2017-11-07 13:38:57 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akuster/morty-next
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/morty-next
Joshua Lock (1):
ruby: fix build of ruby-native with gcc7
Li Zhou (1):
libtiff: Security Advisory - libtiff - CVE-2017-5225
Rajkumar Veer (19):
tiff: Security fix for CVE-2016-10271
tiff: Secruity fix CVE-2016-10093
tiff: Security fix CVE-2016-10268
tiff: Security fix CVE-2016-10266
tiff: Security fix CVE-2016-10267
tiff: Security fix for CVE-2016-10269
tiff: Security fix for CVE-2016-10270
tiff: Security fix for CVE-2017-7592
tiff: Security fix for CVE-2017-7594
tiff: Security fix for CVE-2017-7595
tiff: Security fix for CVE-2017-7596
tiff: Security fix for CVE-2017-7598
tiff: Security fix for CVE-2017-7601
tiff: Security fix for CVE-2017-7602
tiff: Security fix for CVE-2017-7593
curl: Security fix for CVE-2017-1000100
curl: Security fix for CVE-2017-1000101
ruby: Security fix for CVE-2017-14033
ruby: Security fix for CVE-2017-14064
Thiruvadi Rajaraman (14):
curl: Security fix for CVE-2016-8615
curl: Security fix for CVE-2016-8618
curl: Security fix for CVE-2016-8619
curl: Security fix for CVE-2016-8620
curl: Security fix for CVE-2016-8621
curl: Security fix for CVE-2016-8623
curl: Security fix for CVE-2016-8617
curl: Security fix for CVE-2016-8624
curl: Security fix for CVE-2016-9586
ruby: Security fix for CVE-2016-7798
ruby: Security fix for CVE-2017-9227
ruby: Security fix for CVE-2017-9228
ruby: Secruity fix for CVE-2017-9226
ruby: Security fix for CVE-2017-9229
Yi Zhao (1):
tiff: Security fixes
.../recipes-devtools/ruby/ruby/CVE-2016-7798.patch | 164 +++++++++++
.../ruby/ruby/CVE-2017-14033.patch | 89 ++++++
.../ruby/ruby/CVE-2017-14064.patch | 79 ++++++
.../recipes-devtools/ruby/ruby/CVE-2017-9226.patch | 33 +++
.../recipes-devtools/ruby/ruby/CVE-2017-9227.patch | 24 ++
.../recipes-devtools/ruby/ruby/CVE-2017-9228.patch | 26 ++
.../recipes-devtools/ruby/ruby/CVE-2017-9229.patch | 36 +++
meta/recipes-devtools/ruby/ruby/prevent-gc.patch | 32 +++
meta/recipes-devtools/ruby/ruby_2.2.5.bb | 10 +
.../libtiff/files/CVE-2016-10093.patch | 47 ++++
.../libtiff/files/CVE-2016-10266.patch | 60 ++++
.../libtiff/files/CVE-2016-10267.patch | 70 +++++
.../libtiff/files/CVE-2016-10268.patch | 30 ++
.../libtiff/files/CVE-2016-10269.patch | 131 +++++++++
.../libtiff/files/CVE-2016-10270.patch | 134 +++++++++
.../libtiff/files/CVE-2016-10271.patch | 30 ++
.../libtiff/files/CVE-2017-10688.patch | 88 ++++++
.../libtiff/files/CVE-2017-11335.patch | 54 ++++
.../libtiff/files/CVE-2017-7592.patch | 40 +++
.../libtiff/files/CVE-2017-7593.patch | 98 +++++++
.../libtiff/files/CVE-2017-7594-p1.patch | 43 +++
.../libtiff/files/CVE-2017-7594-p2.patch | 50 ++++
.../libtiff/files/CVE-2017-7595.patch | 48 ++++
.../libtiff/files/CVE-2017-7596.patch | 308 +++++++++++++++++++++
.../libtiff/files/CVE-2017-7598.patch | 65 +++++
.../libtiff/files/CVE-2017-7601.patch | 52 ++++
.../libtiff/files/CVE-2017-7602.patch | 69 +++++
.../libtiff/files/CVE-2017-9147.patch | 203 ++++++++++++++
.../libtiff/files/CVE-2017-9936.patch | 46 +++
.../libtiff/files/libtiff-CVE-2017-5225.patch | 92 ++++++
meta/recipes-multimedia/libtiff/tiff_4.0.7.bb | 23 +-
meta/recipes-support/curl/curl/CVE-2016-8615.patch | 71 +++++
meta/recipes-support/curl/curl/CVE-2016-8617.patch | 30 ++
meta/recipes-support/curl/curl/CVE-2016-8618.patch | 49 ++++
meta/recipes-support/curl/curl/CVE-2016-8619.patch | 56 ++++
meta/recipes-support/curl/curl/CVE-2016-8620.patch | 146 ++++++++++
meta/recipes-support/curl/curl/CVE-2016-8621.patch | 104 +++++++
meta/recipes-support/curl/curl/CVE-2016-8623.patch | 174 ++++++++++++
meta/recipes-support/curl/curl/CVE-2016-8624.patch | 68 +++++
meta/recipes-support/curl/curl/CVE-2016-9586.patch | 66 +++++
.../curl/curl/CVE-2017-1000100.patch | 47 ++++
.../curl/curl/CVE-2017-1000101.patch | 94 +++++++
meta/recipes-support/curl/curl_7.50.1.bb | 14 +-
43 files changed, 3191 insertions(+), 2 deletions(-)
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2016-7798.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2017-14033.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2017-14064.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2017-9226.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2017-9227.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2017-9228.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/CVE-2017-9229.patch
create mode 100644 meta/recipes-devtools/ruby/ruby/prevent-gc.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-10093.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-10266.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-10267.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-10268.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-10269.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-10270.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-10271.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-10688.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-11335.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7592.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7593.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7594-p1.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7594-p2.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7595.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7596.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7598.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7601.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-7602.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-9147.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-9936.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/libtiff-CVE-2017-5225.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8615.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8617.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8618.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8619.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8620.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8621.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8623.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-8624.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2016-9586.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2017-1000100.patch
create mode 100644 meta/recipes-support/curl/curl/CVE-2017-1000101.patch
--
2.7.4
reply other threads:[~2017-11-07 16:55 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.1510071393.git.akuster@mvista.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.