From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/at91bootstrap3: fix hash
Date: Thu, 26 Dec 2019 21:59:51 +0100 [thread overview]
Message-ID: <20191226215951.7e821c22@windsurf> (raw)
In-Reply-To: <1577393383-29831-1-git-send-email-pjtexier@koncepto.io>
On Thu, 26 Dec 2019 21:49:43 +0100
Pierre-Jean Texier <pjtexier@koncepto.io> wrote:
> When at91bootstrap3 was bumped to 3.9.0 in commit 513899e471890f4eb677066876890d43ea91b25e,
> an incorrect hash was set.
>
> However, after some checks on the archive with the wrong hash, it appears that it is identical to
> the one with the good hash.
>
> Fixes:
>
> ERROR: at91bootstrap3-v3.9.0.tar.gz has wrong sha256 hash:
> ERROR: expected: 9960b0d18fe42feee566d4c52efa0d7c8251685bf9acfdf343f30a27951ada1e
> ERROR: got : e23e6df23b79ca81e412cb73a1f48bd95df8d46c7d52a1d073c2ed9d4f3a1a71
> ERROR: Incomplete download, or man-in-the-middle (MITM) attack
>
> Reported-by: Ludovic Desroches <ludovic.desroches@microchip.com>
> Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
Did you figure out how you got this bogus archive ? There are really no
differences ? Could you put the bogus archive online somewhere ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-26 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 20:49 [Buildroot] [PATCH] package/at91bootstrap3: fix hash Pierre-Jean Texier
2019-12-26 20:59 ` Thomas Petazzoni [this message]
2019-12-26 21:16 ` Pierre-Jean Texier
2019-12-26 21:34 ` Thomas Petazzoni
2019-12-27 16:15 ` Yann E. MORIN
2019-12-26 22:23 ` 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=20191226215951.7e821c22@windsurf \
--to=thomas.petazzoni@bootlin.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.