From: Yi Zhao <yi.zhao@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] tiff: 2 CVE fixes
Date: Thu, 17 Nov 2016 16:08:08 +0800 [thread overview]
Message-ID: <1479370090-26155-1-git-send-email-yi.zhao@windriver.com> (raw)
Yi Zhao (2):
tiff: Security fix CVE-2016-3658
tiff: Security fix CVE-2016-3632
.../libtiff/files/CVE-2016-3632.patch | 34 ++++++
.../libtiff/files/CVE-2016-3658.patch | 120 +++++++++++++++++++++
meta/recipes-multimedia/libtiff/tiff_4.0.6.bb | 2 +
3 files changed, 156 insertions(+)
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-3632.patch
create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2016-3658.patch
--
2.7.4
next reply other threads:[~2016-11-17 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 8:08 Yi Zhao [this message]
2016-11-17 8:08 ` [PATCH 1/2] tiff: Security fix CVE-2016-3658 Yi Zhao
2016-11-17 8:08 ` [PATCH 2/2] tiff: Security fix CVE-2016-3632 Yi Zhao
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=1479370090-26155-1-git-send-email-yi.zhao@windriver.com \
--to=yi.zhao@windriver.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