From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libopenssl: security bump to version 1.0.2p
Date: Fri, 17 Aug 2018 19:08:54 +0200 [thread overview]
Message-ID: <62cj4fxe0i.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 87a7plcw36.fsf@dell.be.48ers.dk
Am Fri, 17 Aug 2018 09:04:45 +0200 schrieb Peter Korsgaard:
>>>>>> "Bernd" == Bernd Kuhls
>>>>>> <bernd.kuhls@t-online.de> writes:
> > Added upstream sha1 hash.
>
> I'm not sure that really buys us much, but OK.
Hi Peter,
I am just following the manual:
http://buildroot.uclibc.org/downloads/manual/manual.html#adding-packages-
hash
"If upstream provides more than one type of hash (e.g. sha1 and sha512),
then it is best to add all those hashes in the .hash file."
Regards, Bernd
next prev parent reply other threads:[~2018-08-17 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 5:32 [Buildroot] [PATCH 1/1] package/libopenssl: security bump to version 1.0.2p Bernd Kuhls
2018-08-17 7:04 ` Peter Korsgaard
2018-08-17 17:08 ` Bernd Kuhls [this message]
2018-08-17 17:29 ` Peter Korsgaard
2018-08-24 8:41 ` 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=62cj4fxe0i.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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