Article View: borland.public.cppbuilder.internet.socket
Article #1289Indy9 FTP vs Windows FTP
From: Paul at NCF
Date: Fri, 16 Feb 2007 08:58
Date: Fri, 16 Feb 2007 08:58
12 lines
1396 bytes
1396 bytes
Hi, One of the concerns with the standard FTP protocol (used in windows or provided with windows) is that it apparently uses arbitary port numbers for data transfer at the server, which makes tightening up firewalls difficult. It looks like the Indy FTP provides a specific property for the control and data, does this mean that this would make it easier to tightening up firewalls (and for bespoke use, use a different sets of port numbers)? Regards, Paul
Technical Details
Message-ID:
<45d57231@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!203.109.252.33.MISMATCH!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Thread: 11508e,5864cb75bf4a6f79,start X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Paul at NCF" <notplmacca@clara.co.uk> Newsgroups: borland.public.cppbuilder.internet.socket Subject: Indy9 FTP vs Windows FTP Date: Fri, 16 Feb 2007 08:58:53 -0000 Lines: 14 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3028 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 NNTP-Posting-Host: 86.132.251.81 Message-ID: <45d57231@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1171616305 86.132.251.81 (16 Feb 2007 00:58:25 -0800) Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!203.109.252.33.MISMATCH!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail