When ssh1
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 SSH1 The first version of the SSH protocol which provides a way to encrypt network traffic between a client and a server. service.
Port
The port number of the SSH1 service on the remote machine. For SSH1,
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 three types of authentication 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. for connecting to SSH1 servers: password, RSA, and TIS.
Password authentication
transmits the user's password to the server 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.
to authenticate the connection. The transmitted password is protected
from network eavesdropping, due to the cipher encryption of the data channel.
For this reason, some SSH1 servers reject the use of password authentication
if the cipher is set to None
.
RSA authentication uses a public/private key pair to authenticate the connection. The general mechanism behind RSA authentication is that the SSH1 server "challenges" the client A computer or application that uses services provided by a server. to decrypt a message encoded using the user's public key stored on the server. Upon connecting, the SSH1 server generates a random value, encrypts the value using the user's public key and sends the encrypted challenge to the client. The client authenticates the connection by successfully decrypting the challenge using the user's private key. 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. . The first time you connect to an SSH1 server using RSA authentication, SecureCRT will prompt you for the location of this file. Also, prior to using RSA authentication, the public key must be made available to the SSH1 server.
Note: RSA authentication is only supported by the SSH1 protocol and is not an available option for the SSH2 protocol. See Public-Key Authentication for SSH1 to learn more about generating identity files and other setup issues.
TIS firewall authentication uses the TIS firewall server to provide a challenge phrase / response combination. SSH1 servers must be configured to offer TIS authentication
.