From: akuster808 <akuster808@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssh: update to 7.1p2
Date: Thu, 14 Jan 2016 15:45:18 -0800 [thread overview]
Message-ID: <5698330E.504@gmail.com> (raw)
In-Reply-To: <1452785932-32245-1-git-send-email-alexander.kanavin@linux.intel.com>
On 01/14/2016 07:38 AM, Alexander Kanavin wrote:
> This fixes a number of security issues.
>
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
This should apply to Jethro to as its the same version.
- armin
> ---
> .../openssh/{openssh_7.1p1.bb => openssh_7.1p2.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-connectivity/openssh/{openssh_7.1p1.bb => openssh_7.1p2.bb} (97%)
>
> diff --git a/meta/recipes-connectivity/openssh/openssh_7.1p1.bb b/meta/recipes-connectivity/openssh/openssh_7.1p2.bb
> similarity index 97%
> rename from meta/recipes-connectivity/openssh/openssh_7.1p1.bb
> rename to meta/recipes-connectivity/openssh/openssh_7.1p2.bb
> index d81127c..ac824ee 100644
> --- a/meta/recipes-connectivity/openssh/openssh_7.1p1.bb
> +++ b/meta/recipes-connectivity/openssh/openssh_7.1p2.bb
> @@ -24,8 +24,8 @@ SRC_URI = "ftp://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar.
>
> PAM_SRC_URI = "file://sshd"
>
> -SRC_URI[md5sum] = "8709736bc8a8c253bc4eeb4829888ca5"
> -SRC_URI[sha256sum] = "fc0a6d2d1d063d5c66dffd952493d0cda256cad204f681de0f84ef85b2ad8428"
> +SRC_URI[md5sum] = "4d8547670e2a220d5ef805ad9e47acf2"
> +SRC_URI[sha256sum] = "dd75f024dcf21e06a0d6421d582690bf987a1f6323e32ad6619392f3bfde6bbd"
>
> inherit useradd update-rc.d update-alternatives systemd
>
>
prev parent reply other threads:[~2016-01-14 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 15:38 [PATCH] openssh: update to 7.1p2 Alexander Kanavin
2016-01-14 23:45 ` 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=5698330E.504@gmail.com \
--to=akuster808@gmail.com \
--cc=alexander.kanavin@linux.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