From: Thomas Lussnig <lussnig@smcc.net>
To: Rendy V <RendyV@atd.magnus.co.id>
Cc: "'netfilter@lists.samba.org'" <netfilter@lists.samba.org>
Subject: Re: secure ftp with SSL
Date: Fri, 13 Sep 2002 12:20:54 +0200 [thread overview]
Message-ID: <3D81BC06.80107@smcc.net> (raw)
In-Reply-To: 754E53EEA7D3D31194E50050DAB99F6E70543C@thor.id.magnus.com
Rendy V wrote:
> Hi All,
> I have a strange problem, the problem is like this :
> I have an application that use secure ftp and for that reason I have
> opened up the command port (990) with state NEW and allowed data port
> (20000:20049) with state ESTABLISHED, RELATED on the firewall. It
> fails when it try to use data port, for authentication it working just
> fine. Please see the log on the below.
>
> If I open data port 2000:20049 with state NEW it working normally but
> I don't want to make a big hole on my firewall. I suspect that the
> iptables connection tracking cannot track the relation between command
> port and data port because it is encrypted using SSL. Is it true or is
> there something I miss here?? What should I do now??
>
The problem you have is that on SSL crypted connection the RELATED could
not work right. Because for FTP there is an extra module that analyse the
control traffic and can so evalute what ports are related. But this is
not posible then the traffic is unreadable for the module.
Cu Thomas
next prev parent reply other threads:[~2002-09-13 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 3:09 secure ftp with SSL Rendy V
2002-09-13 8:43 ` Roy Sigurd Karlsbakk
2002-09-13 10:09 ` Alistair Tonner
2002-09-13 10:20 ` Thomas Lussnig [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-16 4:21 Rendy V
2002-09-16 8:32 ` Roy Sigurd Karlsbakk
2002-09-17 16:44 ` Alistair Tonner
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=3D81BC06.80107@smcc.net \
--to=lussnig@smcc.net \
--cc=RendyV@atd.magnus.co.id \
--cc=netfilter@lists.samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.