SSH2 Quick
Connect Options
When ssh2 is selected as the Protocol
in the Quick Connect
dialog, the connection A data path or circuit between two computers over a phone line, network cable, or other means. options are as
follows:
Hostname
The hostname or IP address of the remote machine that provides the SSH2 The second version of the SSH protocol which provides a way to encrypt network traffic between a client and a server, with a slightly different set of security features than the SSH1 protocol provides. service.
Port
The port number of the SSH2 service on the remote machine. For SSH2, the default port is 22.
Firewall
If your connection involves a firewall, select your firewall from the list of firewalls that have been configured in the Global Options/Firewall dialog.
Username
The username used to log on to the remote machine.
Authentication group
SecureCRT supports several authentication methods for connecting to SSH2 servers, and will attempt to connect using them in the order that you specify.
Password authentication transmits the user's password to the server to authenticate the connection. The transmitted password is protected from network eavesdropping, due to the cipher encryption The process of converting a data transmission into a secret format that cannot easily be read by unauthorized individuals. See also: decryption. of the data channel.
Note: If the remote machine supports both the SSH2 protocol and changing passwords at the protocol level, the password for an SSH2 session can be changed from the Password Properties dialog, which is accessed by selecting Password in the Authentication group and clicking on the Properties button.
PublicKey authentication uses a public/private key pair to authenticate the connection. During the authentication process, the client A computer or application that uses services provided by a server. and the server negotiate a public key to use for the connection. Once a public key has been determined, the client uses the corresponding private key to perform a signature operation over a unique connection identifier. This signature is then sent to the server for verification. If verification is successful, the client is given permission to connect to the server. The security of the mechanism requires that no one but the owner have access to the private key. The private key is stored locally in an identity file Identity files are two files containing the public-private key pair used to connect to an SSH server using RSA or DSA authentication. The Identity file contains the public and private key pair and is used by SecureCRT. The Identity.pub file contains only the public key which is usually appended to the authorized_keys file. . Also, prior to using public-key authentication, the public key must be made available to the SSH2 server. For more information on generating private-public key pairs, see Public-Key Authentication for SSH2.
Keyboard Interactive authentication allows you to use the keyboard to respond to challenges put forth by the server.
GSSAPI (Generic Security Services Application Program Interface) is a generic API for performing client/server authentication. GSSAPI allows SecureCRT to authenticate with a server without knowing anything about the specific authentication mechanism in use. For more information about using GSSAPI, see the GSSAPI Properties dialog.
SecureCRT also supports the use of X.509 certificates.