From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@vger.kernel.org
Subject: Re: iptables --string-replace
Date: Mon, 17 Jan 2011 07:03:01 -0600 [thread overview]
Message-ID: <20110117130301.GC6659@cardinal> (raw)
In-Reply-To: <AANLkTinzEVbR7L8PU_qhJj4MVXKsAOTKxQfA15ZHUWGT@mail.gmail.com>
On Mon, Jan 17, 2011 at 09:43:27AM +1100, Ben K wrote:
> I'd like to be able to mangle strings passing through my home
> router running Openwrt in order to modify/anonymize user-agent
> strings. I believe a patch further extending the iptables string
> extension by providing string replace functionality was submitted
> by Michael Rash back in 2004 (archived at
> http://www.spinics.net/lists/netfilter/msg23791.html). This would
> be ideal as I could then mangle user-agent headers without eg
> needing to run an http proxy.
I don't see why that's ideal. The proxy solution seems like the
ideal, to me. While an openwrt router might not have the horsepower
needed, neither does it have the horsepower you'll need for string
matching. You're going to have to throw more hardware at this
problem, however you might proceed.
> (BTW what's with the mailing list rejecting HTML emails?! Are we
> living in 2001?)
HTML posting on mailing lists is very rude. I usually ignore them.
Gmail's implementation of it is particularly bad, converting many
arbitrary strings into HTTP URI's.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
prev parent reply other threads:[~2011-01-17 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 22:43 iptables --string-replace Ben K
2011-01-16 23:51 ` Jan Engelhardt
2011-01-16 23:58 ` Ben K
2011-01-17 1:20 ` Jan Engelhardt
2011-01-17 2:44 ` Ben K
2011-01-17 3:41 ` Jan Engelhardt
2011-01-17 10:52 ` Amos Jeffries
2011-01-17 11:27 ` Jan Engelhardt
2011-01-21 10:04 ` Pablo Neira Ayuso
2011-01-21 10:09 ` Jan Engelhardt
2011-01-21 10:24 ` Pablo Neira Ayuso
2011-01-21 10:25 ` Pablo Neira Ayuso
2011-01-17 13:03 ` /dev/rob0 [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=20110117130301.GC6659@cardinal \
--to=rob0@gmx.co.uk \
--cc=netfilter@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