From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Stefan Agner <stefan@agner.ch>,
Christian Stewart <christian@aperture.us>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/2] package/docker-engine: security bump to version v26.0.0
Date: Sun, 28 Apr 2024 17:08:35 +0200 [thread overview]
Message-ID: <87jzkhcyoc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <ZgqmyhHKY0_FZYlA@landeda> (Yann E. MORIN's message of "Mon, 1 Apr 2024 14:21:30 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Christian, All,
> On 2024-03-31 00:46 -0700, Christian Stewart via buildroot spake thusly:
>> Update to the latest major release of docker-engine.
>>
>> Fixes CVE-2024-29018: potential data exfiltration from 'internal' networks via authoritative DNS servers.
>> Do not forward requests to external DNS servers for a container that is only connected to an 'internal' network.
> Please wrap your commit logs to the "standard" ~72 chars width.
>> https://github.com/moby/moby/releases/tag/v26.0.0
>>
>> Signed-off-by: Christian Stewart <christian@aperture.us>
> Applied to master, thanks.
Committed to 2024.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-04-28 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 7:46 [Buildroot] [PATCH v1 1/2] package/docker-engine: security bump to version v26.0.0 Christian Stewart via buildroot
2024-03-31 7:46 ` [Buildroot] [PATCH v1 2/2] package/docker-cli: bump version to v26.0.0 Christian Stewart via buildroot
2024-04-01 12:21 ` Yann E. MORIN
2024-04-28 15:08 ` Peter Korsgaard
2024-04-01 12:21 ` [Buildroot] [PATCH v1 1/2] package/docker-engine: security bump to version v26.0.0 Yann E. MORIN
2024-04-28 15:08 ` 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=87jzkhcyoc.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=stefan@agner.ch \
--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 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.