From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/ncurses: add upstream (security) patches up to 20200118
Date: Wed, 05 Feb 2020 19:26:58 +0100 [thread overview]
Message-ID: <87sgjovqj1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200205161948.GG3131@scaer> (Yann E. MORIN's message of "Wed, 5 Feb 2020 17:19:48 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Peter, Thomas, All,
> On 2020-02-05 14:31 +0100, Thomas De Schampheleire spake thusly:
>> From: Peter Korsgaard <peter@korsgaard.com>
>> Fixes the following security issues:
> [--SNIP--]
>> While we are at it, adjust the white space in the .hash file to match
>> sha256sum output for consistency.
> [--SNIP--]
>> # Locally computed
>> -sha256 86106f0da1cf5ccfa0f0651665dd1b4515e8edad1c7972780155770548b317d9 COPYING
>> +sha256 86106f0da1cf5ccfa0f0651665dd1b4515e8edad1c7972780155770548b317d9 COPYING
> The hash for the license file is now wrong:
>>>> ncurses 6.1 Collecting legal info
> ERROR: COPYING has wrong sha256 hash:
> ERROR: expected:
> 86106f0da1cf5ccfa0f0651665dd1b4515e8edad1c7972780155770548b317d9
> ERROR: got :
> 4d1fde61868c73776a539366dccf5d5a4857e7fd7299efb1f02e07c2afe9ea87
> ERROR: Incomplete download, or man-in-the-middle (MITM) attack
> make[1]: *** [package/ncurses/ncurses.mk:200: ncurses-legal-info] Error 1
> make: *** [Makefile:23: _all] Error 2
> That's because it has been changed by ncurses-6.1-20200104, to change
> the Copyright year.
> Fixed that and pushed, thanks.
Ups, thanks!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-02-05 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 13:31 [Buildroot] [PATCHv2] package/ncurses: add upstream (security) patches up to 20200118 Thomas De Schampheleire
2020-02-05 16:19 ` Yann E. MORIN
2020-02-05 18:26 ` Peter Korsgaard [this message]
2020-03-10 21:32 ` Peter Korsgaard
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=87sgjovqj1.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.