SSH2 Quick Connect Options
From SecureCRT
A data path or circuit between two computers over a phone line, network cable, or other means.
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.
The process of verifying that an individual truly is who he or she claims to be. Supplying a password is a very common method of authentication. The most secure method of authentication supported in SecureCRT is public-key authentication. See also: identity file, public-private key pair.
A computer program that provides services to other computer programs (called clients). Often the computer on which a server program runs is also called a server. The term host is often used as a synonym for server.
An algorithm used to encrypt data at varying levels of security. Examples include 3DES, AES, Blowfish, RC4, and Twofish.
The process of converting a data transmission into a secret format that cannot easily be read by unauthorized individuals. See also: decryption.
A computer or application that uses services provided by a server.
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.
SSH2 Quick Connect Options
When ssh2 is selected as the Protocol
in the Quick Connect
dialog, the connection
options are as follows:
Hostname
The hostname or IP address of the remote machine that provides the SSH2 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
SecureCRT supports two 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 cipherencryption of the data channel.
Unsave Password
This button is only active if Password
has been selected as on of the Authentication methods.
Press this button to have SecureCRT forget the password when this session
closes.
PublicKey authentication uses a public/private key pair to authenticate the connection. During the authentication process, the client 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. 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.
SecureCRT also supports the use of X.509 certificates.
Properties
This button is only active if PublicKey
has been selected as on of the Authentication methods.
Press this button to display the Public Key Properties
dialog