Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Oskar Andreasson <oan@frozentux.net>
To: Marcin Giedz <marcin.giedz@eulerhermes.pl>
Cc: netfilter@lists.netfilter.org
Subject: Re: question
Date: Thu, 27 Oct 2005 12:04:50 +0200	[thread overview]
Message-ID: <1130407490.8832.10.camel@laptop3> (raw)
In-Reply-To: <200510271140.34417.marcin.giedz@eulerhermes.pl>

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

Hi Marcin, 

iptables and netfilter will not do the job, unless you are willing to
sacrifice stability and security. The problem is that the strings that
netfilter will see are broken down into smaller pieces. So the string
"iptables and netfilter" might actually be transmitted as "iptables and"
and then "netfilter" in a separate packet. On top of this, people might
try to intentionally break your filters by fragmenting the above string
into "i", "p", "t", ... etc packets. 

The good thing to do in this case, is to wait until the TCP stream has
reached the application layer and has been reassembled properly. Hence,
you will want to either write your own proxy, or to use someone elses
proxy. 

If you want to use it, I just uploaded a tunnel/proxy program to
http://www.frozentux.net/stunnel.tgz. This is an unfinished program I
started on a couple of years ago. It is written in C. It is horribly
coded and pretty much sucks, but it has no memory leaks and might serve
as a starting point.

Have a nice day;).


On Thu, 2005-10-27 at 11:40 +0200, Marcin Giedz wrote:
> Dnia czwartek, 27 października 2005 11:09, Ruprecht Helms napisał:
> > Marcin Giedz wrote:
> > > I don't get it :(
> > > How with tcpdump as tcpdump is only dump traffic tool - as I know it
> > > can't change anything or I'm wrong?
> >
> > You are right. As I know it only dump.
> > What you need is a hexeditor or you are looking for a tool that do
> > hexediting in the fly.
> 
> Absolutely! 
> 
> >
> > But that is offtopic in this list.
> 
> But I really don't know where to start? Perhaps some did it earlier.
> 
> Marcin
> 
> >
> > Regards,
> > Ruprecht
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-10-27 10:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27  7:55 question Marcin Giedz
2005-10-27  8:18 ` question Ruprecht Helms
2005-10-27  8:39   ` question Marcin Giedz
2005-10-27  9:09     ` question Ruprecht Helms
2005-10-27  9:28       ` question Sorin Panca
2005-10-27  9:40       ` question Marcin Giedz
2005-10-27 10:04         ` Oskar Andreasson [this message]
2005-10-27 10:25           ` question Marcin Giedz
2005-10-27 10:37             ` question Oskar Andreasson
2005-10-27 11:18               ` question Marcin Giedz
2005-10-27 13:28                 ` question Oskar Andreasson
  -- strict thread matches above, loose matches on Subject: below --
2008-04-28  9:01 Question Karim Reda Fakhir
2008-04-28 10:11 ` Question Jan Engelhardt
2008-04-29  1:51   ` Question Diego Lacerda
2006-06-21 12:14 question Fabio S. Silva
2006-06-21 12:23 ` question Sietse van Zanen
2003-09-25 14:04 question emiliano
2003-06-12 22:11 question George Vieira
2003-06-12 20:41 question Sander Sneekes
2002-06-21 17:33 Question Krish Ahya
2002-06-21 17:40 ` Question Antony Stone
2002-06-21 18:31   ` Question James Mello
2002-06-21 23:12     ` Question Antony Stone
2002-06-21 23:16       ` Question James Mello
2002-06-21 23:26         ` Question Antony Stone
2002-06-22  2:11       ` Question Jack Bowling
2002-06-22 15:25         ` Question Stephen Frost
2002-06-22 15:42           ` Question Ramin Alidousti
2002-06-21 18:59 ` Question Nick Drage
2002-06-21 19:41   ` Question Rowan Reid
2002-06-22  0:26 ` Question Sascha Reissner

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=1130407490.8832.10.camel@laptop3 \
    --to=oan@frozentux.net \
    --cc=marcin.giedz@eulerhermes.pl \
    --cc=netfilter@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox