From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Christian Stewart <christian@aperture.us>,
Anisse Astier <anisse@astier.eu>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/go: security bump to version 1.19.11
Date: Fri, 25 Aug 2023 18:05:50 +0200 [thread overview]
Message-ID: <87wmxj9kf5.fsf@48ers.dk> (raw)
In-Reply-To: <20230712215100.4f35aa53@windsurf> (Thomas Petazzoni via buildroot's message of "Wed, 12 Jul 2023 21:51:00 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> On Tue, 11 Jul 2023 15:14:56 -0700
> Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
>> go1.19.11 (released 2023-07-11) includes a security fix to the net/http package,
>> as well as bug fixes to cgo, the cover tool, the go command, the runtime, and
>> the go/printer package.
>>
>> CVE-2023-29406 and Go issue https://go.dev/issue/60374
>>
>> Signed-off-by: Christian Stewart <christian@aperture.us>
>> ---
>> package/go/go.hash | 2 +-
>> package/go/go.mk | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
> Applied to master, thanks.
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-25 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 22:14 [Buildroot] [PATCH 1/1] package/go: security bump to version 1.19.11 Christian Stewart via buildroot
2023-07-12 19:51 ` Thomas Petazzoni via buildroot
2023-08-25 16:05 ` Peter Korsgaard [this message]
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=87wmxj9kf5.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=anisse@astier.eu \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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