From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnutls: security bump to 3.6.7.1
Date: Wed, 3 Apr 2019 21:56:16 +0200 [thread overview]
Message-ID: <20190403215616.5c7882f6@windsurf> (raw)
In-Reply-To: <b8fc60a6fc72431a6caa166bd3ebb19a01077cb8.camel@spectralink.com>
Hello Stefan,
On Wed, 3 Apr 2019 08:11:35 +0000
"S?rensen, Stefan" <Stefan.Sorensen@spectralink.com> wrote:
> On Wed, 2019-04-03 at 10:01 +0200, Peter Korsgaard wrote:
>
> > These issues were fixed in 3.6.7, weren't they? I don't see 3.6.7.1
> > announced yet, what is the delta?
>
> Guess I might have jumped the gun a bit...
>
> Only change is that a file was missing from the release tarball:
> https://gitlab.com/gnutls/gnutls/issues/745
There is a 3.6.7.1 tarball: https://www.gnupg.org/ftp/gcrypt/gnutls/v3.6/
However, your patch breaks legal-info for gnutls:
ERROR: doc/COPYING has wrong sha256 hash:
ERROR: expected: 8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903
ERROR: got : e79e9c8a0c85d735ff98185918ec94ed7d175efc377012787aebcf3b80f0d90b
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
Note: don't do just a hash update: compare the COPYING file
before/after the bump, and document the change in the commit log to
explain why the hash has changed.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-03 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 6:14 [Buildroot] [PATCH] gnutls: security bump to 3.6.7.1 Sørensen, Stefan
2019-04-03 8:01 ` Peter Korsgaard
2019-04-03 8:11 ` Sørensen, Stefan
2019-04-03 19:56 ` Thomas Petazzoni [this message]
2019-04-07 20:54 ` Peter Korsgaard
2019-04-14 21:17 ` 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=20190403215616.5c7882f6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox