From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Patrick McHardy <kaber@trash.net>,
Michal Kubecek <mkubecek@suse.cz>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
netfilter-devel@vger.kernel.org, linux-sctp@vger.kernel.org,
Vlad Yasevich <vyasevich@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [RFC PATCH -next] netfilter: nf_ct_sctp: validate vtag for new conntrack entries
Date: Thu, 26 Nov 2015 15:12:29 +0000 [thread overview]
Message-ID: <20151126151229.GA3412@salvia> (raw)
In-Reply-To: <20151126150726.GD32716@breakpoint.cc>
On Thu, Nov 26, 2015 at 04:07:26PM +0100, Florian Westphal wrote:
> I would prefer to NOT force people to use extra connection tracking code
> for sctp if they don't need it.
>
> Most distributions will ship with all of this as '=m', but IMHO its safe
> to assume that most users will in fact not use sctp (but conntrack for
> udp and tcp).
Enabling features through modprobe seems not to be a good idea
anymore, now we've got namespaces.
We should probably go back to the idea of explicit conntrack
configuration through rules that we discussed many times before.
WARNING: multiple messages have this Message-ID (diff)
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Patrick McHardy <kaber@trash.net>,
Michal Kubecek <mkubecek@suse.cz>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
netfilter-devel@vger.kernel.org, linux-sctp@vger.kernel.org,
Vlad Yasevich <vyasevich@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [RFC PATCH -next] netfilter: nf_ct_sctp: validate vtag for new conntrack entries
Date: Thu, 26 Nov 2015 16:12:29 +0100 [thread overview]
Message-ID: <20151126151229.GA3412@salvia> (raw)
In-Reply-To: <20151126150726.GD32716@breakpoint.cc>
On Thu, Nov 26, 2015 at 04:07:26PM +0100, Florian Westphal wrote:
> I would prefer to NOT force people to use extra connection tracking code
> for sctp if they don't need it.
>
> Most distributions will ship with all of this as '=m', but IMHO its safe
> to assume that most users will in fact not use sctp (but conntrack for
> udp and tcp).
Enabling features through modprobe seems not to be a good idea
anymore, now we've got namespaces.
We should probably go back to the idea of explicit conntrack
configuration through rules that we discussed many times before.
next prev parent reply other threads:[~2015-11-26 15:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 19:13 [RFC PATCH -next] netfilter: nf_ct_sctp: validate vtag for new conntrack entries Marcelo Ricardo Leitner
2015-11-25 19:13 ` Marcelo Ricardo Leitner
2015-11-25 19:42 ` Pablo Neira Ayuso
2015-11-25 19:42 ` Pablo Neira Ayuso
2015-11-25 20:20 ` Marcelo Ricardo Leitner
2015-11-25 20:20 ` Marcelo Ricardo Leitner
2015-11-25 20:58 ` Michal Kubecek
2015-11-25 20:58 ` Michal Kubecek
2015-11-26 9:51 ` Pablo Neira Ayuso
2015-11-26 9:51 ` Pablo Neira Ayuso
2015-11-26 12:52 ` Marcelo Ricardo Leitner
2015-11-26 12:52 ` Marcelo Ricardo Leitner
2015-11-26 14:15 ` Patrick McHardy
2015-11-26 14:33 ` Florian Westphal
2015-11-26 14:33 ` Florian Westphal
2015-11-26 14:49 ` Patrick McHardy
2015-11-26 15:07 ` Florian Westphal
2015-11-26 15:07 ` Florian Westphal
2015-11-26 15:11 ` Patrick McHardy
2015-11-26 15:12 ` Pablo Neira Ayuso [this message]
2015-11-26 15:12 ` Pablo Neira Ayuso
2015-11-26 15:24 ` Patrick McHardy
2015-11-26 15:54 ` Pablo Neira Ayuso
2015-11-26 15:54 ` Pablo Neira Ayuso
2015-11-26 16:02 ` Patrick McHardy
2015-11-26 16:15 ` Pablo Neira Ayuso
2015-11-26 16:15 ` Pablo Neira Ayuso
2015-11-26 16:25 ` Patrick McHardy
2015-11-26 16:43 ` Pablo Neira Ayuso
2015-11-26 16:43 ` Pablo Neira Ayuso
2015-11-26 16:53 ` Patrick McHardy
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=20151126151229.GA3412@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=kaber@trash.net \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=mkubecek@suse.cz \
--cc=netfilter-devel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.