I received an answer to my support request.
In short: FTPS is supported with Explicit TLS (AUTH TLS command is issued on a regular FTP session to upgrade it to a secure one).
To quickly test (on a Mac):
Code:
curl -u <username> -v --ssl-reqd ftp://ftps.freehostia.com
You can also use hosts ftps[1-5].us.freehostia.com but due to the wildcard certificate *.freehostia.com you will also need to supply the '--insecure' flag to ignore certificate validation.
Here's the full reply from the support ticket:
Quote:
FTP/S commonly runs on port 990 and sometimes on port 21, the primary difference being that port 990 is an Implicit FTP/S, and port 21 is an Explicit FTP/S. If a client connects to an FTP/S server on port 990, the assumption is that the client intends to perform SSL. Therefore, the SSL handshake takes place immediately; it is referred to as Implicit because the port number implies security. FTP clients who connect on port 21 and intend to use SSL for security will need to take the extra step to explicitly state their intentions by sending an AUTH SSL or AUTH TLS command to the server. Once the server receives this command, the two parties perform an SSL handshake and enter a secure state—hence why port 21 is referred to as Explicit. This allows the client the opportunity to activate greater security when necessary, or speed the process up on less security-sensitive file transfers.