From: Florian Westphal <fw@strlen.de>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, dborkman@redhat.com
Subject: Re: [PATCH nf] netfilter: conntrack: disable generic protocol tracking
Date: Thu, 25 Sep 2014 17:04:16 +0200 [thread overview]
Message-ID: <20140925150416.GC26716@breakpoint.cc> (raw)
In-Reply-To: <alpine.DEB.2.10.1409251626160.14369@blackhole.kfki.hu>
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu> wrote:
> Without conntrack, you don't have NAT.
Right.
> Without conntrack, you don't have a direction. So how do you controll who
> may initiate the connection for the protocols which are covered by the
> generic tracker? We don't have any match for that.
Fair enough, I'll add autoprobing for the generic tracker instead.
> The generic tracker can know which protocols have an own tracker and when
> it's not available can refuse to track that flow (like the proposed patch
> but selectively, just in this very case).
OK. I think this is acceptable compromise.
> Exploitable modules can be blacklisted temporarily, while the fix is not
> available. With a generic tracker which refuses to track protocols with
> own trackers, the current security issue is not opened up.
Right, thanks Jozsef.
> NEW and ESTABLISHED states, which means directions and thus policies.
> Those are all lost without the generic tracker.
Yes, that and loss of NAT are sound arguments.
Cheers,
Florian
prev parent reply other threads:[~2014-09-25 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 11:32 [PATCH nf] netfilter: conntrack: disable generic protocol tracking Florian Westphal
2014-09-25 12:21 ` Jozsef Kadlecsik
2014-09-25 12:57 ` Florian Westphal
2014-09-25 13:47 ` Jozsef Kadlecsik
2014-09-25 14:13 ` Florian Westphal
2014-09-25 14:48 ` Jozsef Kadlecsik
2014-09-25 15:04 ` Florian Westphal [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=20140925150416.GC26716@breakpoint.cc \
--to=fw@strlen.de \
--cc=dborkman@redhat.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
/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).