Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@eurodev.net>
To: Noman Liaquat <khankhn1@yahoo.com>
Cc: netfilter-devel@lists.netfilter.org, rob@sterenborg.info,
	george.john@ch.easynet.net, mbr@cipherdyne.org,
	ishwar@pali.cps.cmich.edu, netfilter@lists.netfilter.org
Subject: Re: STring Replacement Patch [Quick Response]
Date: Thu, 29 Dec 2005 12:43:34 +0100	[thread overview]
Message-ID: <43B3CBE6.1090908@eurodev.net> (raw)
In-Reply-To: <20051229104208.27463.qmail@web35912.mail.mud.yahoo.com>

Noman Liaquat wrote:
> I  have downloaded the version of patch-o-matic-ng
> from netfilter websites and now my patch of string
> controlling is working, below command is the proof of
> that

the string match is available since kernel 2.6.14, so you don't need
pom-ng in any way.

> #iptables -A FORWARD -m string --algo bm --string
> "hello" -j DROP
> 
> ok that is fine. is there any way to alter that
> packet. to replace--string
> is there any patch available, if yes so how i can
> implement that patch. 

No, this functionality isn't implemented yet: The only sane way to do
this that I see at the moment is implementing a target called `STRING'.
Matches don't allow packet modifications. See the API requirements:

static int match(const struct sk_buff *skb, ...)
                  ^^^

So, such target must implement the same features than the current
`string' match does plus the --replace-string thing.

-- 
Pablo


  reply	other threads:[~2005-12-29 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-29 10:42 STring Replacement Patch [Quick Response] Noman Liaquat
2005-12-29 11:43 ` Pablo Neira Ayuso [this message]
2005-12-29 15:07   ` Problem in patch-o-matic-ng Amresh Kumar
2005-12-29 16:30 ` STring Replacement Patch [Quick Response] Richard Pickett
2005-12-30 17:47   ` /dev/rob0
2006-01-01  9:31     ` Richard Pickett

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=43B3CBE6.1090908@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=george.john@ch.easynet.net \
    --cc=ishwar@pali.cps.cmich.edu \
    --cc=khankhn1@yahoo.com \
    --cc=mbr@cipherdyne.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=rob@sterenborg.info \
    /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