Difference between revisions of "FTPS using Explicit TLS howto (Server)"

From FileZilla Wiki
Jump to navigationJump to search
m (Reverted edits by 151.41.240.213 (talk) to last revision by Auri)
Tag: Rollback
(96 intermediate revisions by 55 users not shown)
Line 1: Line 1:
 
== Configuration ==
 
== Configuration ==
 +
First, you'll want to create a certificate, this can be used in the Certificate Generator in FileZilla Server.  The Generator will want the country code, state, city, etc...
 +
Be as truthful as possible, you only undermine your own credibility if you enter wrong information into the certificate.
  
First you'll want to create a certificate, this can be used in the Certificate Generator in FileZilla Server. The Generator will want country code, state, city, etc..  This information doesn't need to be correct at all, it is just used to generate the hash used to encrypt and decrypt the data being sent by the server and client.  
+
The key size for the certificate is chosen at the top of the generator: 1280 bit, 2048 bit, 4096 bit.
 +
The bigger the key size the more secure the certificate and the initial session key exchange on every connection will be. There is however one thing that needs to be taken into account, CPU utilization during the connection handshake.  When you apply encryption to your FileZilla server the CPU will have to do many calculations to encrypt the data being sent and decrypt the data being received.
 +
Bandwidth will also play a factor in how much the CPU is being utilized. If you have a slower connection, let's say around 1.5Mbps up you may not have to worry about CPU utilization as much.  The best way to decide is to test.
  
Encryption strength for the certificate is chosen at the top of the generator: 1024bit, 2048bit, 4096bit.
+
Please note that FZS needs the paths to the certificate files:
The bigger the hash encryption the more secure the data and account information will be.  There is however one thing that needs to be taken into account, CPU utilization.  When you apply encryption to your FileZilla server the CPU will have to do many calculations to encrypt the data being sent and decrypt the data being received.
+
If you generate your own private key and certificate without putting a path in front of the file name, FZS only puts the bare filename in the certificate field without an error notice, but later you will get "Could not load certificate file" errors in the FZS log when someone tries to connect via FTPS/FTPES (Implicit/Explicit).
Bandwidth will also play a factor in how much the CPU is being utilized. If you have a slower connection, lets say around 1.5mbps up you may not have to worry about CPU utilization as much.  The best way to decide is to test.
 
After you have created the Certificate enter its location into the "Private key file" field, or browse to it.
 
  
If your server has a direct connection to the internet the configuration is simple, check "Enable SSL/TLS Support".
+
Therefore always put the full path to the private key and certificate files in their corresponding fields and FZS can find the files.
 +
 
 +
After you have created the certificate enter its name and folder path location into the "Private key file" field or browse to it. 
 +
 
 +
If your server has a direct connection to the internet the configuration is simple, check "Enable FTP over TLS support (FTPS)".
 +
 
 +
More FTPS documentation is available [[FTP over TLS|here]].
  
 
== Configure with NAT ==
 
== Configure with NAT ==
If you are behind NAT the transmission process can be tricky.  If you are setting up SSL/TLS you may have seen "425 data connection could not be opened".  While using NAT and using SSL/TLS you can't use Active FTP you have to use passive.  Passive is a client side option, but passive doesn't use port 20 and 21. To minimize the available ports open to the internet you will want to set a custom range of ports. In the "Passive mode settings" menu in the server you'll want to check "Use custom port range:" set the ports you want to use for passive mode.  Make sure you add these ports to port forwarding on your NAT device (Router).
+
Please read the [[Network Configuration]] guide for instructions on how to configure the server behind NAT devices (Router, Firewall, etc).
  
Enable Explicit SSL/TLS
+
== Enable Explicit FTP over TLS ==
In the SSL/TLS settings menu check "allow Explicit SSL/TLS on normal connections."  I recommend also checking "Force Explicit SSL/TLS" and "Force PROT P to encrypt data Channel in SSL/TLS mode.This will further enforce encryption policies. If you only want certain groups or users to have encryption you can set that up in the user or group editor.  If there is data you still want available to the general public the "Force" setting should be disabled in the server settings menu, as you will need an FTP client rather than a web browser to access the FTP server.
+
On the TLS settings page check "allow Explicit FTP over TLS."  It is recommended to also check "Disallow plain unencrypted FTP" and "Force PROT P to encrypt file transfers when using FTP over TLS". This will further enforce encryption policies; here PROT "P" is for "Private" as opposed to "C" for clear text. If you only want certain groups or users to have encryption you can set that up in the user or group editor.  If there is data you still want available to the general public the "Force" setting should be disabled in the server settings menu, as you will need an FTP client rather than a web browser to access the FTP server. If using "PROT P - Private",  the client may require a matching TLS setting or it may default to PROT C.
  
 +
Another option you should enable is "Require TLS session resumption on data connection when using PROTP P" as it protects against data connection theft.
  
Setting up your FTP server in this way allows you to encrypt your data and login information without having to get 3rd party programs. With explicit SSL/TLS you will need a FTP client. Internet Explorer and Firefox don't support SSL/TLS without special plugins. ..
+
Setting up your FTP server in this way allows you to encrypt your data and login information without having to get 3rd party programs. With explicit TLS you will need an FTP client. Internet Explorer and Firefox don't support TLS without special plugins. FileZilla client supports FTPS both implicit (FTPS:// protocol), and explicit (FTPES://).

Revision as of 23:51, 21 June 2021

Configuration

First, you'll want to create a certificate, this can be used in the Certificate Generator in FileZilla Server. The Generator will want the country code, state, city, etc... Be as truthful as possible, you only undermine your own credibility if you enter wrong information into the certificate.

The key size for the certificate is chosen at the top of the generator: 1280 bit, 2048 bit, 4096 bit. The bigger the key size the more secure the certificate and the initial session key exchange on every connection will be. There is however one thing that needs to be taken into account, CPU utilization during the connection handshake. When you apply encryption to your FileZilla server the CPU will have to do many calculations to encrypt the data being sent and decrypt the data being received. Bandwidth will also play a factor in how much the CPU is being utilized. If you have a slower connection, let's say around 1.5Mbps up you may not have to worry about CPU utilization as much. The best way to decide is to test.

Please note that FZS needs the paths to the certificate files: If you generate your own private key and certificate without putting a path in front of the file name, FZS only puts the bare filename in the certificate field without an error notice, but later you will get "Could not load certificate file" errors in the FZS log when someone tries to connect via FTPS/FTPES (Implicit/Explicit).

Therefore always put the full path to the private key and certificate files in their corresponding fields and FZS can find the files.

After you have created the certificate enter its name and folder path location into the "Private key file" field or browse to it.

If your server has a direct connection to the internet the configuration is simple, check "Enable FTP over TLS support (FTPS)".

More FTPS documentation is available here.

Configure with NAT

Please read the Network Configuration guide for instructions on how to configure the server behind NAT devices (Router, Firewall, etc).

Enable Explicit FTP over TLS

On the TLS settings page check "allow Explicit FTP over TLS." It is recommended to also check "Disallow plain unencrypted FTP" and "Force PROT P to encrypt file transfers when using FTP over TLS". This will further enforce encryption policies; here PROT "P" is for "Private" as opposed to "C" for clear text. If you only want certain groups or users to have encryption you can set that up in the user or group editor. If there is data you still want available to the general public the "Force" setting should be disabled in the server settings menu, as you will need an FTP client rather than a web browser to access the FTP server. If using "PROT P - Private", the client may require a matching TLS setting or it may default to PROT C.

Another option you should enable is "Require TLS session resumption on data connection when using PROTP P" as it protects against data connection theft.

Setting up your FTP server in this way allows you to encrypt your data and login information without having to get 3rd party programs. With explicit TLS you will need an FTP client. Internet Explorer and Firefox don't support TLS without special plugins. FileZilla client supports FTPS both implicit (FTPS:// protocol), and explicit (FTPES://).