From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] flot: add hash file
Date: Sun, 31 Jan 2016 10:43:13 +0100 [thread overview]
Message-ID: <20160131104313.1c5fdd0a@free-electrons.com> (raw)
In-Reply-To: <rs5uncx00j.ln2@ID-313208.user.individual.net>
Hello,
On Sat, 30 Jan 2016 08:38:35 +0100, Bernd Kuhls wrote:
> I downloaded the tarball
> http://www.flotcharts.org/downloads/flot-0.8.3.tar.gz
> today and got a different sha256 checksum:
>
> ERROR: flot-0.8.3.tar.gz has wrong sha256 hash:
> ERROR: expected:
> d6bddb781ce8ab8bba82c535a0767c22e606cabd9dbb484027b8ff375a193952
> ERROR: got :
> ef9a873befe3ff5ea42ebf1c3657887265a1717744ca8ed0c2bd3dd736d16b21
> ERROR: Incomplete download, or man-in-the-middle (MITM) attack
I checked locally, and in my BR2_DL_DIR, I still have a tarball that
has the
d6bddb781ce8ab8bba82c535a0767c22e606cabd9dbb484027b8ff375a193952 hash,
but indeed if I re-download it, I get a tarball with the
ef9a873befe3ff5ea42ebf1c3657887265a1717744ca8ed0c2bd3dd736d16b21 hash.
> Shall I send a patch?
Yes, please do. It would also be great to notify upstream that they
shouldn't change their tarballs.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-31 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 20:32 [Buildroot] [git commit] flot: add hash file Thomas Petazzoni
2016-01-30 7:38 ` Bernd Kuhls
2016-01-31 9:43 ` Thomas Petazzoni [this message]
2016-01-31 20:08 ` Arnout Vandecappelle
2016-01-31 20:12 ` 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=20160131104313.1c5fdd0a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.