Re: FTPs

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

I would strongly recommend HTTPS over FTPS.  FTPS must either drop the 
encrypted channel after the password (which can be a security problem) 
or else struggles to navigate firewalls/NAT gateways.    Like all FTP, 
it uses a range of ephemeral ports -- which can also be very ugly in a 
firewall setup.

So use https.  That way the whole conversation can be protected, and you 
don't have the ugly firewall problems.

Or use SSH (SFTP), which also works extremely well.

FTPAPI does not (currently) support SSL enhanced FTP.  But the native 
client provided by IBM does.

HTTPAPI does fully support SSL.


On 4/20/2010 8:08 AM, jmmckee wrote:
> I know this has been discussed at length.  I received a request this morning to send/receive data using either FTPS or HTTPS.  This would be a daily process.  I really don't want to have to do this manually.  They also feel that this is something that can be done in two weeks.  The meeting to discuss this is 90 minutes away.  Gotta love how decisions get made.
>
> I would prefer to use sFTP, as I am doing that now.  But, that does not appear to be an option.
>
> My employer passes thru a private network to a corporate office and from there to the outside world.  They are very picky about ports and IP addresses, requiring advance clearance for any port or address.
>
> Is there a redbook detailing how to set up FTPs properly?  I have read references over the past few months about certificates, but have no experience with this.
>
> With time being a factor, I am not sure Scott's FTPAPI would be an option.  Would it, though?
>
>
> John McKee