User Manual

IP Establishing Sessions
6-13
If you are the privileged user, the host’s key is permanently added to the table of known hosts (stored in /
flash/ssh/known_hosts).
Figure 6-31: Outgoing SSH Connections for Privileged User
For each following connection between the SCS and that host, the host’s key will be compared to that stored
in the known host table. If the key is authentic, the connection will automatically proceed to user
authentication.
If the key has changed, you will receive a warning and a brief list of possible explanations including a
possible man-in-the-middle attack. To successfully connect, erase that host’s public key from the
known_hosts file on the SCS, then attempt the connection again. The SCS will note that the host is not
recognized.
The ssh command can be followed by an optional command that will be executed on the remote machine,
and then the session will end. Place the command in quotes to maintain capitalization. The following
command will log user mary into host athena, provide a complete list of files including modification dates
and ownership, and then log mary out of the host.
Figure 6-32: Outgoing SSH Connection with Command
Outgoing SSH connections may be set as the preferred or dedicated service for a port. For more information,
see Preferred/Dedicated Hosts on page 8-8.
6.5.2.5 Troubleshooting SSH Connections
SSH connections require many correct configurations for both the client and the server. If you are having
problems, verify that the following are configured on the server:
◆ The server is running and is network accessible.
◆ SSH is running. To verify, open your SCS’s web browser interface and click on the Authentication
section. The SSH status should be “Running.”
◆ Local authentication is set to precedence 1 (Show Authentication).
◆ Local authentication for users is set (Show Authentication Users).
Verify that the following are configured properly on the client:
◆ The client can connect to the server. Test this by telnetting to the SCS.
◆ The client’s SSH is configured properly. Verify that the method of encryption is set to 3DES.
◆ The client’s login name matches the Server’s local authentication user database.
Local_9>> ssh athena
%Info: The authenticity of host ‘athena’ can't be established.
RSA key fingerprint is 5f:d0:d7:69:39:d1:ca:fb:71:eb:g4:33:b1:ba:8c:e9.
%Warning: Added ‘athena’ (RSA) to the list of known hosts.
mary@athena's password:
Local_2>> ssh athena mary “ls -l”
mary@athena’s password: (not echoed)