Hi,
FTPS is piece of cake using...
System.Net.FtpWebRequest & FtpWebResponse
For SSL obviously you need to set the EnableSsl to true... but the trick is
that you need to add a callback handler for the Certificate Validation.
ServicePointManager.ServerCertificateValidationCallback =
delegate(Object obj, X509Certificate cert, X509Chain
chain, SslPolicyErrors errors)
{
// need to handle SSL exceptions here
return true;
};
For SFTP... this is free and works
http://www.tamirgal.com/blog/page/SharpSSH.aspx
Cheers,
Shane
On 19 November 2010 15:32, Alastair Waddell
<alastair.wadd...@dsc.wa.gov.au>wrote:
> FTP(S)
>
>
>
> -----Original Message-----
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *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 <da...@codify.com> wrote:
>
> On 19 November 2010 15:10, Alastair Waddell <
> alastair.wadd...@dsc.wa.gov.au> 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* | da...@codify.com | 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
> Address Info: 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.*
>
> **
>
--
Cheers,
Shane
DISCLAIMER NOTICE
The contents of this email are confidential. If you are not the intended
recipient, you must not disclose, copy or use the contents in anyway. If
you have received this email in error, please delete it and notify us by
reply email. It is the recipient's responsibility to screen this message
and any attachments for computer viruses.
Thank you.
