FTP(S)


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of David Connors
Sent: Friday, 19 November 2010 1:17 PM
To: ozDotNet
Subject: Re: Secure FTP



On 19 November 2010 15:16, David Connors <[email protected]> wrote:

On 19 November 2010 15:10, Alastair Waddell
<[email protected]> wrote:

No



There are two types of secure FTP and you need to work out if you want
to support SFTP and/or FTPS. The former is based on SSH. The latter is
based on SSL (PKI, authenticity as well as encryption). FTPS is the more
modern/'correct' (for want of a better term) one to use.



The two protocols are completely different, so your first task is to
figure out what you are going to connect to on the server end before
looking at libraries.



Sorry, I meant to add, this assumes that when you say secure FTP you
really mean a secure variant of FTP in the literal sense. There are
other options like WebDAV over HTTP over SSL.


--
David Connors | [email protected] <mailto:[email protected]>  |
www.codify.com <http://www.codify.com>
Software Engineer
Codify Pty Ltd
Phone: +61 (7) 3210 6268 | Facsimile: +61 (7) 3210 6269 | Mobile: +61
417 189 363
V-Card: https://www.codify.com/cards/davidconnors
<https://www.codify.com/cards/davidconnors>
Address Info: https://www.codify.com/contact
<https://www.codify.com/contact>






Important Notice
This email contains information which is confidential and intended solely for 
the use of the individual or entity to whom it is addressed.  Please notify the 
sender immediately if you have received this e-mail by mistake and delete this 
email from your system.  If you are not the intended recipient, any form of 
distribution, copying or use of this communication or the information contained 
or attached is strictly prohibited.  Although Disability Services Commission 
has taken reasonable precautions to ensure no viruses are present in this 
email, the Commission cannot accept responsibility for any loss or damage 
arising from the use of this email or attachments.


Reply via email to