From: Anil Gunturu <anil@mistletoetech.com>
To: netfilter@lists.netfilter.org, Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: tcp conn tracking
Date: Mon, 15 Jan 2007 09:24:41 -0800 (PST) [thread overview]
Message-ID: <33219704.200191168881881760.JavaMail.root@smtp1.mistletoetech.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0701151759250.23841@yvahk01.tjqt.qr>
OK. Does the same thing apply to ftp when NAT is involved? If the port command comes fragmented and out-of-order, and the conntrack module doesn't reassemble the packets, the "inside" ip address goes out untranslated. Is this considered a security breach.
Cheers,
-Anil
----- Original Message -----
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Anil Gunturu <anil@mistletoetech.com>
Cc: netfilter@lists.netfilter.org, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Sent: Monday, January 15, 2007 8:59:48 AM GMT-0800 US/Pacific
Subject: Re: tcp conn tracking
>So, ftp connection tracking doesn't work always. Just curious about
>what is the rationale for such a solution? Is it assumed that if the
>packet with PORT command is fragmented someone is deliberatly attacking
>the system?
Yes you can assume that. FTP commands are usually not that long to not
fit into a small packet.
-`J'
--
next prev parent reply other threads:[~2007-01-15 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 5:14 tcp conn tracking Anil Gunturu
2007-01-15 7:47 ` Jozsef Kadlecsik
2007-01-15 16:57 ` Anil Gunturu
2007-01-15 16:59 ` Jan Engelhardt
2007-01-15 17:24 ` Anil Gunturu [this message]
2007-01-15 18:42 ` Jozsef Kadlecsik
2007-01-15 18:49 ` Grant Taylor
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=33219704.200191168881881760.JavaMail.root@smtp1.mistletoetech.com \
--to=anil@mistletoetech.com \
--cc=jengelh@linux01.gwdg.de \
--cc=kadlec@blackhole.kfki.hu \
--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