FTP over TLS: Difference between revisions

From FileZilla Wiki
Jump to navigationJump to search
m (Reverted edits by 91.121.152.54 (talk) to last revision by CodeSquid)
Line 1: Line 1:
== Setup ==
== Setup ==


=== Server Setup ===
Very strange for Google who does a deecnt job in my opinion of offering (or even enforcing)(as it must be) TLS everywhere else, except for here. Does not make any sense. Worse, they do not seem to share the reason why. (I'm sure there must be one, but they won't share it, or so it seems based on searching the interwebs on this). It is time they add this. Come on!, google.Thanks all! Cheers.Jason
 
Open the admin interface, and go to settings. Choose SSL/TLS (FTPS) settings, and choose to generate a new certificate. The two digit country code can be found by googleing (United States is just US - it can be confusing that two digit can be two letters, and not necessarily two numbers only).  
 
Once you have generated the certificate, and chosen where to save it, filezilla will auto fill in the private key file, and the certificate file fields to point to the generated certificate.
 
At this point, you can either choose to allow SSL/TLS if the user opts, or you can force them to always use SSL/TLS, and not allow them to connect if they do not use it.
 
PROT P refers to the data transfers. Communication with the server is always encrypted if you use SSL/TLS.<br>
Communication encrypted: PROT C, Communication+Data encrypted: PROT P.
 
If PROT P isn't enforced, client could send PROT C and transfer files unencrypted. If PROT P is enforced, PROT C is rejected.
 
Also see [[FTPS_using_Explicit_SSL/TLS_howto_(Server)|FTPS using Explicit SSL/TLS howto (Server)]].


=== Client Setup ===
=== Client Setup ===

Revision as of 12:03, 23 July 2012

Setup

Very strange for Google who does a deecnt job in my opinion of offering (or even enforcing)(as it must be) TLS everywhere else, except for here. Does not make any sense. Worse, they do not seem to share the reason why. (I'm sure there must be one, but they won't share it, or so it seems based on searching the interwebs on this). It is time they add this. Come on!, google.Thanks all! Cheers.Jason

Client Setup

For a client to connect to a server using SSL, then the host for that connection needs to be set to FTPS. In FileZilla client this means prefixing the host with "FTPES://" for "explicit" FTPS, or "FTPS://" for the legacy "implicit" FTPS.

Certificate Removal

The file trustedcerts.xml contains certificates for secure websites that you have told your FileZilla client to trust connections to. This file should not be confused with any certificates you have in use if you use FileZilla as a server as well.

Windows

In order to remove a saved certificate, navigate to %APPDATA%\FileZilla and delete, rename or modify the trustedcerts.xml file.

Linux

In order to remove a saved certificate rename or modify the file ~/.filezilla.

Explicit vs Implicit FTPS

FTPS (SSL/TLS) is served up in two incompatible modes. If using explicit FTPS, the client connects to the normal FTP port and explicitly switches into secure (SSL/TLS) mode with "AUTH TLS", whereas implicit FTPS is an older style service that assumes SSL/TLS mode right from the start of the connection (and normally listens on TCP port 990, rather than 21). In a FileZilla client this means prefixing the host with "FTPES://" to connect an "explicit" FTPS server, or "FTPS://" for the legacy "implicit" server (for which you will likely also need to set the port to 990).

SSL/TLS (FTPS) vs SSH (SFTP)

FTPS (FTP encrypted with SSL/TLS) should not be confused with SFTP (SSH). The latter is a completely different protocol, with more information here.

Retrieved from "https://wiki.filezilla-project.org/wiki/index.php?title=FTP_over_TLS&oldid=17651"