Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org, liezhi.yang@windriver.com
Subject: [jethro-next 0/1] Pull request for git fixes
Date: Sun, 31 Jan 2016 14:34:28 -0800	[thread overview]
Message-ID: <cover.1454279467.git.akuster@mvista.com> (raw)

From: Armin Kuster <akuster@mvista.com>

This appears to be more of an issue on the server side.

The following changes since commit e3b1402971e6aaff7ba3dd864f786f1c32745bf1:

  glibc-locale: fix QA warning (2016-01-31 11:54:21 -0800)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib akuster/jethro_cve_fixes
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/jethro_cve_fixes

Armin Kuster (1):
  git: Security fix CVE-2015-7545

 .../git/git-2.5.0/0008-CVE-2015-7545-1.patch       | 446 +++++++++++++++++++++
 .../git/git-2.5.0/0009-CVE-2015-7545-2.patch       | 112 ++++++
 .../git/git-2.5.0/0010-CVE-2015-7545-3.patch       | 112 ++++++
 .../git/git-2.5.0/0011-CVE-2015-7545-4.patch       | 150 +++++++
 .../git/git-2.5.0/0012-CVE-2015-7545-5.patch       |  69 ++++
 meta/recipes-devtools/git/git_2.5.0.bb             |   8 +
 6 files changed, 897 insertions(+)
 create mode 100644 meta/recipes-devtools/git/git-2.5.0/0008-CVE-2015-7545-1.patch
 create mode 100644 meta/recipes-devtools/git/git-2.5.0/0009-CVE-2015-7545-2.patch
 create mode 100644 meta/recipes-devtools/git/git-2.5.0/0010-CVE-2015-7545-3.patch
 create mode 100644 meta/recipes-devtools/git/git-2.5.0/0011-CVE-2015-7545-4.patch
 create mode 100644 meta/recipes-devtools/git/git-2.5.0/0012-CVE-2015-7545-5.patch

-- 
2.3.5



             reply	other threads:[~2016-01-31 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 22:34 Armin Kuster [this message]
2016-01-31 22:34 ` [jethro-next 1/1] git: Security fix CVE-2015-7545 Armin Kuster

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.1454279467.git.akuster@mvista.com \
    --to=akuster808@gmail.com \
    --cc=liezhi.yang@windriver.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