All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Michael Chi <chibo.michael@gmail.com>,
	netfilter-devel@vger.kernel.org, fw@strlen.de
Subject: Re: does nftables support string match?
Date: Wed, 13 Sep 2017 14:54:20 +0200	[thread overview]
Message-ID: <20170913125420.GA2453@breakpoint.cc> (raw)
In-Reply-To: <20170913124745.GA2943@salvia>

Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> Cc'ing Florian,
> 
> On Wed, Sep 13, 2017 at 08:13:38PM +0800, Michael Chi wrote:
> > Hi experts,
> > 
> > We are using nftables instead of iptables, but after I have search all
> > the nftables documents I found, I don't find a corresponding match
> > that can match string in packet, like following in iptables:
> > iptables -A INPUT -m string --string 'badstring' -j DROP
> > 
> > Is such function supported by nftables?
> 
> I remember he's got a patch to add support for this, still to be
> upstreamed.

The decision at nfws was to not upstream this, iirc, due to the fact
that this mandates linear evaluation.  Instead we talked about adding
application offset.

> Moreover, I started on a patchset to add a new application layer
> offset that we discussed during NFWS:
> 
> https://workshop.netfilter.org/2017/wiki/images/8/8c/Nft-l7.pdf
> 
> So we can solve the existing limitation in iptables, since we start
> matching after IP header offset.

Right.  IIRC you also planned to add some way to describe the userspace
headers including ability to skip variable-sized content or search for
a start-marker so one could e.g. move to a particular offset and then
extract content.

This would allow to combine it with set lookups, and just have a set of
strings to do a lookup in.

Michael, what are you trying to match? dns lookups? tls sni hostname?

      reply	other threads:[~2017-09-13 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 12:13 does nftables support string match? Michael Chi
2017-09-13 12:47 ` Pablo Neira Ayuso
2017-09-13 12:54   ` 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=20170913125420.GA2453@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=chibo.michael@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 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.