From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Fido pull request
Date: Thu, 18 Feb 2016 11:04:39 +0000 [thread overview]
Message-ID: <1455793479.3642.2.camel@linux.intel.com> (raw)
In-Reply-To: <cover.1455631402.git.joshua.g.lock@intel.com>
On Tue, 2016-02-16 at 14:30 +0000, Joshua Lock wrote:
> Please consider the following fixes for inclusion in the Fido branch.
>
> - libpcre security fix not required in jethro or master because the
> newer
> version they carry isn't affected
> - backport a fix for some memory leaks in rpmresolve
> - backport a fix for kernel.bbclass which already exists in jethro &
> master
> - remove a stray tzdata file, this change isn't required for jethro
> or master as
> the file isn't present in those branches
I've added two more changes to the branch since Tuesday:
- libbsd fix for CVE-2016-2090 backported from Jethro
- glibc fix for CVE-2015-7547 based on the change in Jethro and
master only with the patch from the 2.21 branch of glibc
Regards,
Joshua
prev parent reply other threads:[~2016-02-18 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 14:25 [PATCH 0/4] Fido pull request Joshua Lock
2016-02-16 14:30 ` Joshua Lock
2016-02-16 14:28 ` Joshua G Lock
2016-02-18 11:04 ` Joshua G Lock [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=1455793479.3642.2.camel@linux.intel.com \
--to=joshua.g.lock@linux.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 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.