From: Peter Korsgaard <peter@korsgaard.com>
To: "TIAN Yuanhao" <tianyuanhao3@163.com>
Cc: Christian Stewart <christian@aperture.us>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/2] package/docker-engine: backport fix for host header check
Date: Wed, 06 Sep 2023 21:00:09 +0200 [thread overview]
Message-ID: <87tts7gm9y.fsf@48ers.dk> (raw)
In-Reply-To: <5deecbea.4d7e.1897700fbb6.Coremail.tianyuanhao3@163.com> (TIAN Yuanhao's message of "Fri, 21 Jul 2023 13:51:40 +0800 (CST)")
>>>>> "TIAN" == TIAN Yuanhao <tianyuanhao3@163.com> writes:
> Tested-by: TIAN Yuanhao <tianyuanhao3@163.com>
> At 2023-07-17 12:10:46, "Christian Stewart via buildroot" <buildroot@buildroot.org> wrote:
>> Go 1.20.6 and 1.19.11 include a security check of the http Host header:
>>
>> https://github.com/golang/go/issues/60374
>>
>> docker-cli does not satisfy this check:
>>
>> $ docker exec -it ctr bash
>> http: invalid Host header
>>
>> This is a backported patch to fix this issue:
>>
>> Issue: https://github.com/moby/moby/issues/45935
>> Upstream PR: https://github.com/moby/moby/pull/45942
>>
>> The upstream PR has been merged and will be included in v24.0.5.
>>
>> Signed-off-by: Christian Stewart <christian@aperture.us>
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-09-06 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 4:10 [Buildroot] [PATCH v1 1/2] package/docker-engine: backport fix for host header check Christian Stewart via buildroot
2023-07-17 4:10 ` [Buildroot] [PATCH v1 2/2] package/docker-cli: " Christian Stewart via buildroot
2023-07-21 5:50 ` TIAN Yuanhao
2023-09-06 19:01 ` Peter Korsgaard
2023-07-21 5:51 ` [Buildroot] [PATCH v1 1/2] package/docker-engine: " TIAN Yuanhao
2023-09-06 19:00 ` 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=87tts7gm9y.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=tianyuanhao3@163.com \
/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.