From: David Gibson <david@gibson.dropbear.id.au>
To: Jan Wrobel <jan@mixedbit.org>
Cc: passt-user@passt.top
Subject: Re: Auto forwarding ports, but only to localhost
Date: Fri, 28 Nov 2025 12:10:32 +1100 [thread overview]
Message-ID: <aSj2iG1GeRbwSfJB@zatzit> (raw)
In-Reply-To: <CACm05o8+8FRr9KGVq+wF7BcnwRR9XXi5QyuDvArv9GiT=xXnrw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
On Thu, Nov 27, 2025 at 01:48:54PM +0100, Jan Wrobel wrote:
> Hi,
>
> For pasta, would you consider an option to enable automatic forwarding
> of ports bound in a namespace, but make the forwarded ports available
> only via localhost, not all addresses?
>
> I'm working on a sandboxing program which uses pasta. The option -t
> "auto" is super convenient, but requires extra care, without proper
> firewall setup bound ports become automatically available to outside
> world. For a sandboxing program like mine, it is not a safe default to
> run with, because the program shouldn't assume the user will have a
> firewall configured.
>
> If something like "localhost/auto" was supported, it would match the
> convenience of "auto", no manual port mapping config would be needed,
> but would be safer for uses cases where exposing ports to outside
> world is problematic.
Short answer: yes, but it might be a while.
Long answer:
We want to make our forwarding / NAT configuration more flexible in
ways that would allow a bunch of things, including this. There are a
lot of different features people have requested, each individually
simple, but together adding up to quite a lot of work. I'm actively
working on making our internal data structures more flexible to allow
more general configuration. However, it's fairly slow going, between
other firefighting and unravelling some technical debt.
If you want to make sure your specific use case isn't forgotten, the
best way would be to file a ticket for it on passt.top - it will
probably be blocked on https://bugs.passt.top/show_bug.cgi?id=140 but
that will keep a record to look back at later.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-11-28 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 12:48 Jan Wrobel
2025-11-28 1:10 ` David Gibson [this message]
2025-11-28 11:03 ` Jan Wrobel
2025-11-30 7:24 ` David Gibson
2025-11-30 10:42 ` Stefano Brivio
[not found] ` <CACm05o-ZJq9AE1bzc7hZ4YGi2Jy346ZxJ4ra9Pwsx3_AkX-SNA@mail.gmail.com>
2025-12-01 10:32 ` Stefano Brivio
2025-12-01 11:49 ` Jan Wrobel
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=aSj2iG1GeRbwSfJB@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=jan@mixedbit.org \
--cc=passt-user@passt.top \
/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;
as well as URLs for IMAP folder(s).