Telnet Action Security Tab
This tab of the Telnet action specifies security settings for secure Telnet connections.
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.|
|•||SSH: Either SSH 1.0 or SSH 2.0 will be used when establishing a secure connection, based on the version of the protocol that is supported by the server.|
|•||SSH v1: The SSH 1.0 protocol will be used when establishing the connection. This is an older version of the protocol which should not be used unless explicitly required by the server. Most modern SSH server support version 2.0 of the protocol.|
|•||SSH v2: The SSH 2.0 protocol should be used when establishing the connection. This is the default version of the protocol that is supported by most SSH servers.|
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).
Note: Certificate info does not apply for SSH protocols.
Verify host fingerprint: If checked, the specified fingerprint will be compared with the fingerprint value returned by the server, and the step will fail if they do not match. Build the step once to determine the host key, then use the value from the build output here for future use (to prevent man-in-the-middle security attacks). This option applies only for SSH connections.