If SecureNetTerm is used to connect to a host using the telnet protocol, selection is based upon standard telnet protocol specifications for both authentication and encryption. For example, a host may have a Kerberos based authentication telnet server assigned to listen to port 23 and a SRP based authentication telnet server assigned to listen to port 27. The selection of the session cipher is determined by mutual agreement between the host telnet server and SecureNetTerm, however the end user cannot control which is selected. Encryption is not currently supported by any known telnet server using the Microsoft NTLM authentication method. Both client and server certificates are supported.
Anonymous ciphers can include any of the ciphers specified above.
When authentication is performed using an anonymous cipher, SecureNetTerm does a verification of the TLS finished messages to protect against man in the middle attacks. Session traffic can also be optionally compressed prior to encryption by the standard zlib library software algorithms created by Jean-loup Gailly and Mark Adler. The major difference between telnet and SSH is both the authentication and encryption methods can be selected by the user from a list of methods supported by the protocol level, the SSH server and SecureNetTerm. The available encryption methods for SSH-1 are 3DES and Blowfish. The user must provide these as independent Windows based programs.