All of lore.kernel.org
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: otavio@ossystems.com.br,
	openembedded-devel@lists.openembedded.org, akuster808@gmail.com
Subject: [PATCH 0/7][fido] Pull request
Date: Sun,  7 Feb 2016 13:11:52 -0800	[thread overview]
Message-ID: <cover.1454879225.git.akuster@mvista.com> (raw)

From: Armin Kuster <akuster@mvista.com>

Please consider these few Security and build fixes for fido-next

The following changes since commit 220b31d536cf15e68c11980e0c721a7050313db1:

  ntp: upgrade 4.2.8p2 -> 4.2.8p3 (2015-10-26 21:43:09 +0100)

are available in the git repository at:

  git://github.com/akuster/meta-openembedded akuster/fido-next
  https://github.com//tree/akuster/fido-next

Armin Kuster (5):
  squid: serveral missing security fixes
  php: Security fix CVE-2015-7803
  php: Security fix CVE-2015-7804
  php: Security fix CVE-2016-1903
  krb5: Fix warning.

Qi.Chen@windriver.com (1):
  ntp: fix rpath QA issue

Wenzong Fan (1):
  ntp: upgrade 4.2.8p3 -> 4.2.8p4

 .../squid/files/CVE-2014-6270.patch                |  61 +++++
 .../squid/files/CVE-2014-7141_CVE-2014-7142.patch  | 282 ++++++++++++++++++++
 .../squid/files/CVE-2015-3455.patch                |  53 ++++
 .../squid/files/CVE-2015-5400.patch                | 292 +++++++++++++++++++++
 .../recipes-daemons/squid/squid_3.4.7.bb           |   4 +
 .../ntp/{ntp_4.2.8p3.bb => ntp_4.2.8p4.bb}         |   5 +-
 meta-oe/recipes-connectivity/krb5/krb5_1.12.2.bb   |   2 +-
 .../recipes-devtools/php/php/CVE-2015-7803.patch   |  82 ++++++
 .../recipes-devtools/php/php/CVE-2015-7804.patch   |  62 +++++
 .../recipes-devtools/php/php/CVE-2016-1903.patch   |  28 ++
 meta-oe/recipes-devtools/php/php_5.5.21.bb         |   3 +
 11 files changed, 871 insertions(+), 3 deletions(-)
 create mode 100644 meta-networking/recipes-daemons/squid/files/CVE-2014-6270.patch
 create mode 100644 meta-networking/recipes-daemons/squid/files/CVE-2014-7141_CVE-2014-7142.patch
 create mode 100644 meta-networking/recipes-daemons/squid/files/CVE-2015-3455.patch
 create mode 100644 meta-networking/recipes-daemons/squid/files/CVE-2015-5400.patch
 rename meta-networking/recipes-support/ntp/{ntp_4.2.8p3.bb => ntp_4.2.8p4.bb} (97%)
 create mode 100644 meta-oe/recipes-devtools/php/php/CVE-2015-7803.patch
 create mode 100644 meta-oe/recipes-devtools/php/php/CVE-2015-7804.patch
 create mode 100644 meta-oe/recipes-devtools/php/php/CVE-2016-1903.patch

-- 
2.3.5



             reply	other threads:[~2016-02-07 21:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 21:11 Armin Kuster [this message]
2016-02-07 21:11 ` [PATCH 1/7] squid: serveral missing security fixes Armin Kuster
2016-02-07 21:11 ` [PATCH 2/7] ntp: fix rpath QA issue Armin Kuster
2016-02-07 21:11 ` [PATCH 3/7] ntp: upgrade 4.2.8p3 -> 4.2.8p4 Armin Kuster
2016-02-07 21:11 ` [PATCH 4/7] php: Security fix CVE-2015-7803 Armin Kuster
2016-02-07 21:11 ` [PATCH 5/7] php: Security fix CVE-2015-7804 Armin Kuster
2016-02-07 21:11 ` [PATCH 6/7] php: Security fix CVE-2016-1903 Armin Kuster
2016-02-07 21:11 ` [PATCH 7/7] krb5: Fix warning Armin Kuster
2016-02-09 18:08   ` Martin Jansa
2016-02-09 20:27     ` akuster808
2016-02-09 21:41       ` Khem Raj
2016-02-09 23:33         ` akuster808

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.1454879225.git.akuster@mvista.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.