Security Tab

This tab of the FTP action specifies security settings for secure FTP connections.

FTPSecurity

Protocol: Security protocol to use when connecting to the remote server:

•	None: No security protocol will be used

•	SSL, TLS, or PCT: Either the SSL 2.0, SSL 3.0, PCT or TLS protocols will be used when establishing a secure connection. The correct protocol is automatically selected.

•	SSL: Either SSL 2.0 or SSL 3.0 may be used when establishing a secure connection. The correct protocol is automatically selected.

•	TLS: The TLS 1.0 protocol will be used when establishing a secure connection.

•	PCT: The PCT 1.0 protocol will be used when establishing a secure connection.

Options: Options related to the security protocol:

•	Default: specifies that the client should attempt to establish a secure connection with the server. Note that the server must support secure connections using either the SSL, PCT or TLS protocols.

•	AUTH TLS-P: specifies that the client should use the AUTH TLS-P command to negotiate an explicit secure connection. Some servers may only require this when connecting to the server on ports other than 990.

•	AUTH TLS: specifies that the client should use the AUTH TLS command to negotiate an explicit secure connection. This option is provided for compatibility with servers that do not implement the AUTH TLS-P command.

•	AUTH SSL: specifies that the client should use the AUTH SSL command to negotiate an explicit secure connection. This option is provided for compatibility with servers that do not implement the AUTH TLS-P command.

Certificate Info

Location: The location to retrieve the certificate from (user store, machine store, or PFX file).

Store name/file: The name of the store to open or the PFX file to retrieve the certificate from (optional).

Certificate name: Friendly name of the certificate to use (optional). Note that the name must match completely, but the comparison is not case sensitive. If no matching certificate is found, the action will then attempt to find a certificate that has a matching common name (also called the certificate subject). This comparison is less stringent, and the first partial match will be returned. If this second search fails, the action will return an error indicating that the certificate could not be found.

Password: The certificate password (applies only for certificates in a PFX file).

Send commands unencrypted: If checked, the command channel used to send commands to the server and receive command result and status information from the server will not be encrypted. This may be necessary to allow a secure FTP connection through a firewall. Changing the mode for the data channel requires that the server support the PROT command. If this command is not supported by the server, the function will fail and the channel mode will remain unchanged.

Note: The Plink Tunnel action can be used for creating a secure SSH tunnel for use with the FTP action if your server does not support SSL (only authentication, and not data transfer, is encrypted when using FTP over SSH).