From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [dizzy] [PATCH 1/1] glibc: use patch for CVE-2015-1781
Date: Thu, 17 Dec 2015 08:33:49 -0800 [thread overview]
Message-ID: <5672E3ED.9080201@gmail.com> (raw)
In-Reply-To: <1448590536-58100-1-git-send-email-tudor.florea@enea.com>
merged to staging
git@git.yoctoproject.org/poky-contrib.git akuster/dizzy-next
thanks
Armin
On 11/26/2015 06:15 PM, Tudor Florea wrote:
> Patch added to the repo wasn't actually considered due to a
> erronously way of specifying the sources.
>
> Signed-off-by: Tudor Florea <tudor.florea@enea.com>
> ---
> meta/recipes-core/glibc/glibc_2.20.bb | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/meta/recipes-core/glibc/glibc_2.20.bb b/meta/recipes-core/glibc/glibc_2.20.bb
> index a0736cd..2ab4083 100644
> --- a/meta/recipes-core/glibc/glibc_2.20.bb
> +++ b/meta/recipes-core/glibc/glibc_2.20.bb
> @@ -40,14 +40,12 @@ EGLIBCPATCHES = "\
> # file://eglibc-install-pic-archives.patch \
> # file://initgroups_keys.patch \
> #
> -CVEPATCHES = "\
> - file://CVE-2015-1781-resolv-nss_dns-dns-host.c-buffer-overf.patch \
> -"
>
> CVEPATCHES = "\
> file://CVE-2014-7817-wordexp-fails-to-honour-WRDE_NOCMD.patch \
> file://CVE-2012-3406-Stack-overflow-in-vfprintf-BZ-16617.patch \
> file://CVE-2014-9402_endless-loop-in-getaddr_r.patch \
> + file://CVE-2015-1781-resolv-nss_dns-dns-host.c-buffer-overf.patch \
> "
> LIC_FILES_CHKSUM = "file://LICENSES;md5=e9a558e243b36d3209f380deb394b213 \
> file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
>
prev parent reply other threads:[~2015-12-17 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 2:15 [dizzy] [PATCH 1/1] glibc: use patch for CVE-2015-1781 Tudor Florea
2015-12-17 16:33 ` akuster808 [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=5672E3ED.9080201@gmail.com \
--to=akuster808@gmail.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