From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linux-firmware: bump version and fix hash
Date: Wed, 3 Oct 2018 21:40:23 +0200 [thread overview]
Message-ID: <20181003194023.GA2383@scaer> (raw)
In-Reply-To: <CAK4VdL0mu+5Od73gU4T7dRLVRHior7gYg6NQ3+bNKms9P5R=EQ@mail.gmail.com>
Erico, All,
On 2018-10-03 21:11 +0200, Erico Nunes spake thusly:
> On Thu, Sep 27, 2018 at 8:50 PM Peter Korsgaard <peter@korsgaard.com> wrote:
> > > ERROR: linux-firmware-8d69bab7a3da1913113ea98cefb73d5fa6988286.tar.gz has wrong sha256 hash:
> > > ERROR: expected: 905be20e4e2d7628dea4e2e99195520fc0cce8b247faabdc52fc44a3ff2ceb04
> > > ERROR: got : b9fce72a7b0b55eb311701dfd47914bc9e037134fa401d33e6e73ab9ebc9d116
> > > ERROR: Incomplete download, or man-in-the-middle (MITM) attack
> > Hmm, odd?
[--SNIP--]
> I see that the hash got updated again after this commit, and now it's
> broken again for me.
> I re-tested on more machines running Fedora 28 or Centos 7, including
> one where I had never used Buildroot before, and apparently I even get
> different hashes on each for linux-firmware:
>
> ERROR: linux-firmware-44d4fca9922a252a0bd81f6307bcc072a78da54a.tar.gz has wrong sha256 hash:
> ERROR: expected: b279ca4d086887c2efab13e28a7ca36e409410d3df38a62d7c7b5799ee3de916
> ERROR: got : 12d025328deab2bd2bec489c5f51181db6530cc9eb91d10ef66a55c18c2da8bf
[--SNIP--]
Weird; I do get the correct hash:
linux-firmware-44d4fca9922a252a0bd81f6307bcc072a78da54a.tar.gz: OK (sha256: b279ca4d086887c2efab13e28a7ca36e409410d3df38a62d7c7b5799ee3de916)
> Is there some known cause for this?
In the past, this could have been caused by a too-olld or too-recent tar
version. But nowadays, we do build our own tar when we need it. Can you
check what tar Fedora 28 has, and check whether Buildroot built host-tar
or not?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-10-03 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 22:38 [Buildroot] [PATCH 1/1] linux-firmware: bump version and fix hash Erico Nunes
2018-09-27 18:50 ` Peter Korsgaard
2018-10-03 19:11 ` Erico Nunes
2018-10-03 19:40 ` Yann E. MORIN [this message]
2018-10-03 20:08 ` Bernd Kuhls
2018-10-28 7:59 ` Erico Nunes
2018-11-01 14:14 ` Yann E. MORIN
2018-11-01 21:06 ` Yann E. MORIN
2018-11-02 13:05 ` Erico Nunes
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=20181003194023.GA2383@scaer \
--to=yann.morin.1998@free.fr \
--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