From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] openssh upgrade and CVE fix
Date: Wed, 18 May 2016 15:11:28 +0300 [thread overview]
Message-ID: <cover.1463572706.git.jussi.kukkonen@intel.com> (raw)
The CVE fix should apply for at least Krogoth and Jethro as well.
The following changes since commit 7707cf6562e6a477ea953743a2d9aba682d90949:
sdk-manual: Fixed three broken links to sections within manual. (2016-05-17 21:35:00 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib jku/openssh
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/openssh
Jussi Kukkonen (2):
openssh: Upgrade 7.1p2 -> 7.2p2
openssh: Backport fix for CVE-2015-8325
.../openssh/openssh/CVE-2015-8325.patch | 39 +++
.../openssh/openssh/CVE-2016-1907_2.patch | 65 ----
.../openssh/openssh/CVE-2016-1907_3.patch | 329 ---------------------
.../openssh/CVE-2016-1907_upstream_commit.patch | 33 ---
.../openssh/openssh/CVE-2016-3115.patch | 84 ------
.../openssh/{openssh_7.1p2.bb => openssh_7.2p2.bb} | 9 +-
6 files changed, 42 insertions(+), 517 deletions(-)
create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2015-8325.patch
delete mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2016-1907_2.patch
delete mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2016-1907_3.patch
delete mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2016-1907_upstream_commit.patch
delete mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2016-3115.patch
rename meta/recipes-connectivity/openssh/{openssh_7.1p2.bb => openssh_7.2p2.bb} (95%)
--
2.1.4
next reply other threads:[~2016-05-18 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 12:11 Jussi Kukkonen [this message]
2016-05-18 12:11 ` [PATCH 1/2] openssh: Upgrade 7.1p2 -> 7.2p2 Jussi Kukkonen
2016-05-18 12:11 ` [PATCH 2/2][master][krogoth][jethro] openssh: Backport fix for CVE-2015-8325 Jussi Kukkonen
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.1463572706.git.jussi.kukkonen@intel.com \
--to=jussi.kukkonen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox