From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openssh: bump to version 6.7p1
Date: Tue, 07 Oct 2014 21:04:40 +0200 [thread overview]
Message-ID: <87bnpnhfav.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141007190129.GG8276@tarshish> (Baruch Siach's message of "Tue, 7 Oct 2014 22:01:29 +0300")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
>> Because i've found out about the release from another source.
>> Both are equally good though.
> I think this link is worth mentioning in the .hash file. It allows
> the user to verify the hash against an external source, adding to the
> warm and fuzzy feeling that is the whole point of .hash files. This
> is especially important for sensitive packages like OpenSSH.
Agreed.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-10-07 19:04 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
2014-10-07 12:46 ` Gustavo Zacarias
2014-10-07 19:01 ` Baruch Siach
2014-10-07 19:04 ` Peter Korsgaard [this message]
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=87bnpnhfav.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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