From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] popt: add hash file
Date: Tue, 7 Jul 2015 16:53:15 +0200 [thread overview]
Message-ID: <20150707165315.120c39d6@free-electrons.com> (raw)
In-Reply-To: <559BE37B.7090708@zacarias.com.ar>
Dear Gustavo Zacarias,
On Tue, 07 Jul 2015 11:34:35 -0300, Gustavo Zacarias wrote:
> Yes, very subjective though.
> Right now we're fetching from a mirror and that's where the md5 comes from.
> Proper upstream is back but never provided a md5 or sig for the latest
> releases, so that md5 isn't "original".
> I based my calculation on a locally cached popt tarball that predates
> the source change BTW.
> And to be honest hashes that aren't backed by announcements (archived on
> mailing lists that are on separate infra, hence harder to tamper with)
> are worth almost nothing.
Though our policy so far is to have the upstream hash when available,
and if it's too weak complement it with a locally calculated stronger
hash.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-07 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 12:52 [Buildroot] [PATCH 1/4] netstat-nat: add hash file Gustavo Zacarias
2015-07-07 12:52 ` [Buildroot] [PATCH 2/4] rp-pppoe: " Gustavo Zacarias
2015-07-07 12:52 ` [Buildroot] [PATCH 3/4] transmission: " Gustavo Zacarias
2015-07-07 12:52 ` [Buildroot] [PATCH 4/4] popt: " Gustavo Zacarias
2015-07-07 14:17 ` Baruch Siach
2015-07-07 14:19 ` Gustavo Zacarias
2015-07-07 14:27 ` Baruch Siach
2015-07-07 14:34 ` Gustavo Zacarias
2015-07-07 14:53 ` Thomas Petazzoni [this message]
2015-07-07 15:36 ` Gustavo Zacarias
2015-07-10 9:20 ` [Buildroot] [PATCH 1/4] netstat-nat: " Thomas Petazzoni
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=20150707165315.120c39d6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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