Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openssh: bump to version 6.7p1
Date: Tue, 7 Oct 2014 15:39:27 +0300	[thread overview]
Message-ID: <20141007123927.GD8276@tarshish> (raw)
In-Reply-To: <1412680305-28778-1-git-send-email-gustavo@zacarias.com.ar>

Hi Gustavo,

On Tue, Oct 07, 2014 at 08:11:45AM -0300, Gustavo Zacarias wrote:
> Also add hash file.
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/openssh/openssh.hash | 2 ++
>  package/openssh/openssh.mk   | 2 +-
>  2 files changed, 3 insertions(+), 1 deletion(-)
>  create mode 100644 package/openssh/openssh.hash
> 
> diff --git a/package/openssh/openssh.hash b/package/openssh/openssh.hash
> new file mode 100644
> index 0000000..0b57d48
> --- /dev/null
> +++ b/package/openssh/openssh.hash
> @@ -0,0 +1,2 @@
> +# Locally calculated after checking pgp signature
> +sha256	b2f8394eae858dabbdef7dac10b99aec00c95462753e80342e530bbb6f725507	openssh-6.7p1.tar.gz

Why not use the (base64 encoded) hash values from 
http://www.openssh.com/txt/release-6.7? The output of

	echo svg5Tq6Fjau9732sELma7ADJVGJ1PoA0LlMLu29yVQc= |base64 -d |hd

matches your calculated SHA256 AFAICS.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-10-07 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 11:11 [Buildroot] [PATCH] openssh: bump to version 6.7p1 Gustavo Zacarias
2014-10-07 12:39 ` Baruch Siach [this message]
2014-10-07 12:46   ` Gustavo Zacarias
2014-10-07 19:01     ` Baruch Siach
2014-10-07 19:04       ` Peter Korsgaard
2014-10-07 13:38 ` Peter Korsgaard

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=20141007123927.GD8276@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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