From: Patrick McHardy <kaber@trash.net>
To: Joonwoo Park <joonwpark81@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>,
Thomas Graf <tgraf@suug.ch>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH 6/8 v2] netfilter: fix string extension for case insensitive pattern matching
Date: Thu, 26 Jun 2008 13:34:18 +0200 [thread overview]
Message-ID: <48637EBA.6080003@trash.net> (raw)
In-Reply-To: <20080626021241.GA26212@tp64>
Joonwoo Park wrote:
> netfilter: fix string extension for case insensitive pattern matching
>
> The flag XT_STRING_FLAG_IGNORECASE indicates case insensitive string
> matching.
> netfilter can find cmd.exe, Cmd.exe, cMd.exe and etc easily.
>
> Also this patch won't break compatibility since we have 2 bytes space
> between invert and config, due to config was 8 bytes aligned.
> So we can put a new value 'flags' in xt_string_info between invert and
> config safely.
> If previous version of iptables interact with this kernel, to kernel
> side, flags will be set to zero and to user side, flags will be ignored.
This makes it hard for userspace to know whether insensitive
search is supported or not, similar for possible future flag
additions.
Please
- add a new revision for userspace to know whether flags are
supported at all. You don't need to duplicate the checkentry
function for this since the structure layout didn't change,
you can simply parse flags dependant on match->revision.
Userspace can use the existance of the new revision as
indication that flags are supported.
- check for unknown flags and return an error
next prev parent reply other threads:[~2008-06-26 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 10:25 [PATCH 6/8 v2] netfilter: fix string extension for case insensitive pattern matching Joonwoo Park
2008-06-25 11:03 ` Patrick McHardy
2008-06-26 2:12 ` Joonwoo Park
2008-06-26 11:34 ` Patrick McHardy [this message]
2008-06-27 9:49 ` Joonwoo Park
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=48637EBA.6080003@trash.net \
--to=kaber@trash.net \
--cc=joonwpark81@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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).