netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Florian Westphal <fw@strlen.de>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Chris Clayton <chris2553@googlemail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	regressions@lists.linux.dev, netfilter-devel@vger.kernel.org,
	coreteam@netfilter.org
Subject: Re: removing conntrack helper toggle to enable auto-assignment [was Re: b118509076b3 (probably) breaks my firewall]
Date: Mon, 19 Sep 2022 23:27:43 +0200	[thread overview]
Message-ID: <20220919212743.GC3498@breakpoint.cc> (raw)
In-Reply-To: <20220919135715.6057331d@kernel.org>

Jakub Kicinski <kuba@kernel.org> wrote:
> I think we should do _something_ because we broke so many things 
> in this release if we let this rot until its smell reaches Linus -
> someone is getting yelled at...

Well, we can restore the knob and some strongly worded printk.
(or even tain/warn_on_once/whatever).

So its not like we no options, but autoassign=1 is a
problematic configuration and so it would prefer to finally get rid
of it.

> Now, Linus is usually okay with breaking uAPI if there is no other 
> way of preventing a security issue. But (a) we break autoload of
> all helpers and we only have security issue in one,

This isn't 100% correct either, because its not necessarliy about
a security bug.  Helpers (by design) make things reachable that
otherwise would not be, e.g. ftp with 'loose=1' modparam adds a
'from anywhere to x:y' reverse forward, so if client is behind nat
(and the helper is active) this can be used to expose a service to
a 3rd party (granted, this is unlikely, given its off by default).

> and (b) not loading
> the module doesn't necessarily mean removing the file (at least IMHO).

We did not disable module load, but loading a connection tracking
module has no effect anymore without the needed iptables (or nftables)
rules to tell the conntrack engine which connections need to be
monitored by which helper.

  reply	other threads:[~2022-09-19 21:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 19:13 b118509076b3 (probably) breaks my firewall Chris Clayton
2022-09-08 19:19 ` Florian Westphal
2022-09-08 21:22   ` Chris Clayton
2022-09-08 21:48     ` Florian Westphal
2022-09-09 10:19       ` Pablo Neira Ayuso
2022-09-09 18:21         ` Chris Clayton
2022-09-09 18:31           ` Chris Clayton
2022-09-10  2:02           ` removing conntrack helper toggle to enable auto-assignment [was Re: b118509076b3 (probably) breaks my firewall] Pablo Neira Ayuso
2022-09-10  3:49             ` Willy Tarreau
2022-09-19 19:40             ` Jakub Kicinski
2022-09-19 20:23               ` Florian Westphal
2022-09-19 20:57                 ` Jakub Kicinski
2022-09-19 21:27                   ` Florian Westphal [this message]
2022-09-20  6:49                   ` Chris Clayton
2022-09-20  9:01                     ` Thorsten Leemhuis

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=20220919212743.GC3498@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=chris2553@googlemail.com \
    --cc=coreteam@netfilter.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=regressions@lists.linux.dev \
    /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 NNTP newsgroup(s).