RE: FTP-S

-----Original Message-----

Below is the rationale for dropping sFTP. Does this make sense? I get
the impression that the manager believes sFTP (and ssh) is not secure.
Or, that ssh (and sFTP) are not as good as FTP/S.


"The system supports FTPS, which is a tightening of security as it
prevents excessive SSH accounts that can make the server more
vulnerable. "

Yep. I received a later email from their DP manager that stated that

sFTP and FTP-S were identical. Sounds uninformed, to me. Not sure I
was clear after reading my post. I would be client side. We have
TAATOOLS and one tool is FTP2, which seems to provide FTP-S. I guess
my main question, based on having read other adventures with FTP-S
relates to certificates. Are certificates server only, client, or both?
I know that sFTP has to have known hosts on both ends. Isn't this also
true for FTP-S?

John McKee
-----Original message-----
From: Kirk Goins kirkgoins@xxxxxxxxx
Date: Thu, 02 Sep 2010 15:35:50 -0500
To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx
Subject: Re: FTP-S

So just to confirm they are going from a OpenSSH version of FTP to

a SSL

based version?



On Thu, Sep 2, 2010 at 7:20 AM, jmmckee <jmmckee@xxxxxxxxxxxxxx>

wrote:

A vendor has been using sFTP but now has decided that this will

not be used

on a replacement server as od Sep 15. They are switching to FTP-

S on that

date.

Can anybody direct me to documentation on how to use this as a

client?