First Connection with Password

You can connect to a remote host by using sshg3 on the command line:

Enter the sshg3 command using the following syntax:
```
$ sshg3 <hostname>
```
For example:
```
$ sshg3 abc.example.com
```
The basic syntax is:
```
$ sshg3 user@host#port
```
where:
- user - Enter a user name that is valid on the remote host. The user@ attribute is optional. If no user name is given, the local user name is assumed.
- host - Enter the name of the remote host as an IP address, FQDN (fully qualified domain name), or short host name. The remote host must be running a Secure Shell version 2 server.
- port - Enter the number of the Secure Shell listen port on the remote server. The #port attribute is optional. If no port is given, the default Secure Shell port 22 is assumed.
The server authentication phase starts. The server sends its public key to the client for validation (when server public-key authentication is used).
When Tectia Client receives a new host public key, a host identification message is displayed. For example:
```
$ sshg3 user@host
Host key not found from database.
Key fingerprint:
xecic-fifub-kivyh-kohag-zedyn-logum-pycuz-besug-galoh-gupah-xaxby
You can get a public key's fingerprint by running
% ssh-keygen-g3 -F publickey.pub
on the keyfile.
Are you sure you want to continue connecting (yes/no)?
```
The message shows the fingerprint of the host's public key in the SSH Babble format that is a series of pronounceable five-letter words in lower case and separated by dashes.
Verify the validity of the fingerprint, preferably by contacting the administrator of the remote host computer by telephone.
After the fingerprint has been verified and found to be correct, it is safe to save the key and continue connecting.
If you choose to save the server public key, relevant information about the key will be stored on the client host in directory $HOME/.ssh2/hostkeys. After the first connection, the locally stored information about the server public key will be used in server authentication.
The user authentication phase starts. You will be prompted to authenticate yourself to the server with your password.
After the server has successfully authenticated you, the Secure Shell connection to the server is opened.