Re: Explicit FTP over TLS support -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

hi Chris,

Hmmm... my interpretation was the opposite of yours. I assumed that when Bob said "explicit", he meant that the TLS conversation was specified explicitly ( via SECCNN(*IMPLICIT) ) as opposed to negotiated (i.e. SECCNN(*SSL) )

But, I guess he could've meant it either way. Hopefully, Bob will know which one of these matches his requirements.

On 2/9/2012 5:32 PM, Chris Bipes wrote:

Bob,

FTP Client:
At a command line type ftp<F4>
Cursor to the Secure Connection and press<F1>
*IMPLICIT
The FTP client immediately attempts to use TLS/SSL when
connecting to the specified FTP server (without sending an AUTH
subcommand to the server). If the server does not support
implicit TLS/SSL on the specified port, or the TLS/SSL
negotiation fails for any reason, the connection is closed.
*SSL (Explicit)
After connecting to the specified FTP server, the FTP client
sends an AUTH (authorization) subcommand requesting a TLS/SSL
protected session. If the server supports TLS/SSL, a TLS/SSL
negotiation performed. If the server does not support TLS/SSL
or the TLS/SSL negotiation fails, the connection is closed.

This mailing list archive is Copyright 1997-2024 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.