From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v4 0/7] Don't expose container loopback services to the host
Date: Thu, 17 Oct 2024 16:32:57 +1100 [thread overview]
Message-ID: <20241017053304.909386-1-david@gibson.dropbear.id.au> (raw)
podman issue #24045 pointed out that pasta's spliced forwarding logic
can expose services within the namespace bound only to 127.0.0.1 or
::1 to the host. However, the namespace probably expects those to
only be accessible to itself, so that's probably not what we want.
This changes our forwarding logic so as not to do this. Note that the
podman tests will currently fail with this series, I've submitted
podman PR https://github.com/containers/podman/pull/24064 to fix that.
Link: https://github.com/containers/podman/issues/24045
Changes since v3:
* Added several extra patches working around failures on Debian,
because its dhclient-script doesn't wait for DAD to complete
Changes since v2:
* Add new field do structure comment
Changes since v1:
* Add --host-lo-to-ns-lo option to preserve the old behaviour
* Clarify the new behaviour in the man page
* Add some extra patches making some other corrections to the man
page
David Gibson (7):
arp: Fix a handful of small warts
test: Explicitly wait for DAD to complete on SLAAC addresses
test: Wait for DAD on DHCPv6 addresses
passt.1: Mark --stderr as deprecated more prominently
passt.1: Clarify and update "Handling of local addresses" section
test: Clarify test for spliced inbound transfers
fwd: Direct inbound spliced forwards to the guest's external address
arp.c | 8 ++---
conf.c | 9 ++++++
fwd.c | 31 +++++++++++++-----
passt.1 | 75 ++++++++++++++++++++++++++-----------------
passt.h | 2 ++
test/passt/dhcp | 2 ++
test/passt/ndp | 4 ++-
test/passt_in_ns/tcp | 8 ++---
test/passt_in_ns/udp | 4 +--
test/pasta/dhcp | 2 ++
test/pasta/ndp | 3 +-
test/pasta/tcp | 16 ++++-----
test/pasta/udp | 8 ++---
test/two_guests/basic | 6 +++-
14 files changed, 115 insertions(+), 63 deletions(-)
--
2.47.0
next reply other threads:[~2024-10-17 5:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 5:32 David Gibson [this message]
2024-10-17 5:32 ` [PATCH v4 1/7] arp: Fix a handful of small warts David Gibson
2024-10-17 8:45 ` Stefano Brivio
2024-10-18 0:43 ` David Gibson
2024-10-17 5:32 ` [PATCH v4 2/7] test: Explicitly wait for DAD to complete on SLAAC addresses David Gibson
2024-10-17 5:33 ` [PATCH v4 3/7] test: Wait for DAD on DHCPv6 addresses David Gibson
2024-10-17 8:45 ` Stefano Brivio
2024-10-18 1:13 ` David Gibson
2024-10-17 5:33 ` [PATCH v4 4/7] passt.1: Mark --stderr as deprecated more prominently David Gibson
2024-10-17 5:33 ` [PATCH v4 5/7] passt.1: Clarify and update "Handling of local addresses" section David Gibson
2024-10-17 5:33 ` [PATCH v4 6/7] test: Clarify test for spliced inbound transfers David Gibson
2024-10-17 5:33 ` [PATCH v4 7/7] fwd: Direct inbound spliced forwards to the guest's external address David Gibson
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=20241017053304.909386-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).