public inbox for passt-user@passt.top
 help / color / mirror / Atom feed
From: Jan Wrobel <jan@mixedbit.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-user@passt.top
Subject: Re: Auto forwarding ports, but only to localhost
Date: Fri, 28 Nov 2025 12:03:06 +0100	[thread overview]
Message-ID: <CACm05o8k6J22jpK5SE9e-gi4xHA-eZiOhfstfKcf6ChA_YW_rA@mail.gmail.com> (raw)
In-Reply-To: <aSj2iG1GeRbwSfJB@zatzit>

On Fri, Nov 28, 2025 at 2:10 AM David Gibson
<david@gibson.dropbear.id.au> wrote:
>
> 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.

Thanks, for considering adding this feature!

I'll add the ticket, but currently there is some problem with the
passt ticket system. I've seen it working at some point but today and
yesterday https://passt.top/passt/bugs is just an empty page, and
https://bugs.passt.top/index.cgi gives 403 error

Cheers,
Jan

  reply	other threads:[~2025-11-28 11:03 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
2025-11-28 11:03   ` Jan Wrobel [this message]
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=CACm05o8k6J22jpK5SE9e-gi4xHA-eZiOhfstfKcf6ChA_YW_rA@mail.gmail.com \
    --to=jan@mixedbit.org \
    --cc=david@gibson.dropbear.id.au \
    --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).