From: Joshua G Lock <joshua.g.lock@linux.intel.com>
To: Armin Kuster <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org, akuster@mvista.com
Subject: Re: [fido][PATCH 00/11] Fido Security fixes #2
Date: Mon, 29 Feb 2016 15:17:06 +0000 [thread overview]
Message-ID: <1456759026.3164.19.camel@linux.intel.com> (raw)
In-Reply-To: <cover.1456278327.git.akuster@mvista.com>
On Tue, 2016-02-23 at 17:48 -0800, Armin Kuster wrote:
> From: Armin Kuster <akuster@mvista.com>
>
> please consider these changes for the next fido update.
>
> This is to meet our obligation for Yocto compatibility
>
> The following changes since commit
> 9037f2c7c797367c2d09b87f344ecf749d28cb41:
>
> gdk-pixbuf: Security fix CVE-2015-7674 (2016-02-22 19:08:53 -0800)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib akuster/fido_cve_fixes
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/fi
> do_cve_fixes
>
> Armin Kuster (10):
> busybox: Security fix CVE-2011-5325
This doesn't appear to actually fix anything, it just adds this patch
which notes a potential security issue:
https://git.busybox.net/busybox/commit/?id=a116552869db5e7793ae10968eb3
c962c69b3d8c
> libpng: Security fix CVE-2015-8126
> libpng: Security fix CVE-2015-8472
> libgcrypt: Security fix CVE-2015-7511
> curl: Security fix CVE-2016-0754
> curl: Secuirty fix CVE-2016-0755
> bind: Security fix CVE-2015-8461
> nettle: Security fix CVE-2015-8803 and CVE-2015-8805
> nettle: Security fix CVE-2015-8804
> git: Security fixes CVE-2015-7545
>
> Li Zhou (1):
> rpcbind: Security Advisory - rpcbind - CVE-2015-7236
Queued in joshuagl/fido-next
Regards,
Joshua
prev parent reply other threads:[~2016-02-29 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 1:48 [fido][PATCH 00/11] Fido Security fixes #2 Armin Kuster
2016-02-29 15:17 ` 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=1456759026.3164.19.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox