Re: Converting one FTP to SSL FTP -- MIDRANGE-L

Subject: Re: Converting one FTP to SSL FTP
From: Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>
Date: Mon, 1 Feb 2010 16:57:38 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Mon, Feb 1, 2010 at 15:33, Lowary, Jim <jlowary@xxxxxxxx> wrote:

I've looked at the archives on this but still confused. ÂI have an FTP
to a business that I'm wanting to convert to FTPS (I think that is SSL
FTP), this would be outbound only.

There are many ways to do encrypted FTP

Traditional FTP, TCP Port 21 (and 20, Active & Passive Mode)
Traditional FTP with implicit SSL, TCP Port 990 (and 989, Active & Passive Mode)
Traditional FTP with explicit SSL (STARTTLS), TCP Port 21 (and 20,
Active & Passive Mode)
SFTP with SSH as transport, TCP Port 22, this is a completely new
protocal that doesn't have anything to do with Traditional FTP.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.