From: Andras Kis-Szabo <kisza@securityaudit.hu>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Netfilter Devel <netfilter-devel@lists.netfilter.org>,
Netdev <netdev@oss.sgi.com>,
usagi-core@linux-ipv6.org
Subject: Re: [Patch]: IPv6 Connection Tracking
Date: 25 Sep 2003 21:07:18 +0200 [thread overview]
Message-ID: <1064516837.995.49.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0309252151180.11253-100000@netcore.fi>
Hi,
> What I fear is that in the end, nothing gets done because having the goal
> set to perfection. If there is no energy to drive through the
> L3-independent connecting tracking, the end result is that the user does
> not have this feature (remember ip6tables REJECT target? That must have
> been sitting in netfilter for some 2+ years, and not having been
> integrated in the mainline kernel and the users still do not have the
> feature!).
I have felt the same on Brad Chapman's port. That code has lost in time
:(
> > Your FTP code uses EPSV and EPRT from rfc2428. What's about the FOOBAR
> > RFC (1639)? OK, it's a joke :)
> > Could we open an IPv4 data connection next to the IPv6 controll
> > connection?
> What about LPRT and LPSV?
This is the rfc1639/foobar :)
Regards,
kisza
--
Andras Kis-Szabo Security Development, Design and Audit
-------------------------/ Zorp, NetFilter and IPv6
kisza@SecurityAudit.hu /------------------------------------------->
next prev parent reply other threads:[~2003-09-25 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 5:21 [Patch]: IPv6 Connection Tracking Yasuyuki Kozakai
2003-09-25 9:28 ` Harald Welte
2003-09-25 10:50 ` [netfilter-core] " Jozsef Kadlecsik
2003-09-25 10:51 ` David S. Miller
2003-09-25 13:10 ` Yasuyuki Kozakai
2003-10-03 11:19 ` Yasuyuki Kozakai
2003-10-07 12:30 ` Harald Welte
2003-09-25 18:48 ` Andras Kis-Szabo
2003-09-25 18:57 ` Pekka Savola
2003-09-25 19:07 ` Andras Kis-Szabo [this message]
2003-09-25 19:14 ` Pekka Savola
2003-09-29 8:42 ` Harald Welte
2003-09-26 3:54 ` Yasuyuki Kozakai
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=1064516837.995.49.camel@localhost \
--to=kisza@securityaudit.hu \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pekkas@netcore.fi \
--cc=usagi-core@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).