From: John Keeping <john@metanate.com>
To: buildroot@busybox.net
Subject: [Buildroot] linux-firmware hash mismatch (tar-1.30)
Date: Tue, 9 Jan 2018 16:15:31 +0000 [thread overview]
Message-ID: <20180109161531.47ec21e0.john@metanate.com> (raw)
Hi,
I'm getting the following error cloning linux-firmware:
ERROR: linux-firmware-17e6288135d4500f9fe60224dce2b46d850c346b.tar.gz has wrong sha256 hash:
ERROR: expected: 28d359523a36c1cdc3e85a8e148bb2d68b036d28b10f0e80a192f3dc29f02c16
ERROR: got : bf6fe8d7620949a3e771954cb6d9d18dcf000d37ecc910a7cf69723c1798e246
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
After a bit of digging, it looks like this is caused by tar-1.30 which
includes the following fix:
* --numeric-owner now affects private headers too.
Comparing the tarball created on my system with one from
sources.buildroot.net gives the output like this, which shows that the
uname/gname fields are set for a GNUTYPE_LONGNAME record in the version
from sources.buildroot.net and not set in the version created with
tar-1.30:
-- >8 --
@@ -669379,24 +669379,24 @@
00a36c20: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36c30: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36c40: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36c50: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36c60: 0000 0000 3030 3030 3634 3400 3030 3030 ....0000644.0000
00a36c70: 3030 3000 3030 3030 3030 3000 3030 3030 000.0000000.0000
00a36c80: 3030 3030 3135 3600 3030 3030 3030 3030 0000156.00000000
-00a36c90: 3030 3000 3031 3136 3035 0020 4c00 0000 000.011605. L...
+00a36c90: 3030 3000 3030 3737 3735 0020 4c00 0000 000.007775. L...
00a36ca0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36cb0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36cc0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36cd0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36ce0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36cf0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
-00a36d00: 0075 7374 6172 2020 0072 6f6f 7400 0000 .ustar .root...
+00a36d00: 0075 7374 6172 2020 0000 0000 0000 0000 .ustar ........
00a36d10: 0000 0000 0000 0000 0000 0000 0000 0000 ................
-00a36d20: 0000 0000 0000 0000 0072 6f6f 7400 0000 .........root...
+00a36d20: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36d30: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36d40: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36d50: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36d60: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36d70: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36d80: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00a36d90: 0000 0000 0000 0000 0000 0000 0000 0000 ................
-- 8< --
I'm not sure whether anything can be done to avoid this problem, but
hopefully reporting it will save the next person some debugging time.
Regards,
John
next reply other threads:[~2018-01-09 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 16:15 John Keeping [this message]
2018-01-10 19:15 ` [Buildroot] linux-firmware hash mismatch (tar-1.30) Peter Korsgaard
2018-01-11 10:55 ` John Keeping
2018-01-14 13:30 ` Yann E. MORIN
2018-01-17 23:28 ` Arnout Vandecappelle
2018-01-18 21:40 ` Peter Korsgaard
2018-01-22 22:14 ` Arnout Vandecappelle
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=20180109161531.47ec21e0.john@metanate.com \
--to=john@metanate.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