From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] flex & gnutls fixes
Date: Mon, 10 Oct 2016 11:34:17 +0300 [thread overview]
Message-ID: <cover.1476087291.git.jussi.kukkonen@intel.com> (raw)
Backported cve fixes for flex and gnutls.
Also minor improvement to error handling in depexp.
- Jussi
The following changes since commit b9d6a7cc234f44e44e5421191924b7463e9c0a9d:
bitbake: main: Check bitbake server-only port is a number (2016-10-09 12:33:26 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib jku/m4-fixes
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/m4-fixes
Jussi Kukkonen (4):
gnutls: Backport certificate check fix
flex: Update upstream check uri
flex: Backport buffer overflow fix
depexp: Close UI with error message on NoProvider event
bitbake/lib/bb/ui/depexp.py | 24 +++++++++
.../recipes-devtools/flex/flex/CVE-2016-6354.patch | 59 ++++++++++++++++++++++
meta/recipes-devtools/flex/flex_2.6.0.bb | 3 ++
.../gnutls/gnutls/CVE-2016-7444.patch | 35 +++++++++++++
meta/recipes-support/gnutls/gnutls_3.5.3.bb | 1 +
5 files changed, 122 insertions(+)
create mode 100644 meta/recipes-devtools/flex/flex/CVE-2016-6354.patch
create mode 100644 meta/recipes-support/gnutls/gnutls/CVE-2016-7444.patch
--
2.1.4
next reply other threads:[~2016-10-10 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 8:34 Jussi Kukkonen [this message]
2016-10-10 8:30 ` [PATCH 1/4] gnutls: Backport certificate check fix Jussi Kukkonen
2016-10-10 8:30 ` [PATCH 2/4] flex: Update upstream check uri Jussi Kukkonen
2016-10-10 8:30 ` [PATCH 3/4] flex: Backport buffer overflow fix Jussi Kukkonen
2016-10-10 8:30 ` [PATCH 4/4] depexp: Close UI with error message on NoProvider event Jussi Kukkonen
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.1476087291.git.jussi.kukkonen@intel.com \
--to=jussi.kukkonen@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