Secure Shell (SSH) Concepts Storage Management Initiative Specification

This topic provides an overview of the Secure Shell (SSH) and its use from a host system that is running a remote SSH client.

Overview

Secure Shell (SSH) is a client-server network application. The SAN Volume Controller cluster acts as the SSH server in this relationship. The SSH client provides a secure environment in which to connect to a remote machine. It uses the principles of public and private keys for authentication.

SSH keys are generated by the SSH software. This includes a public key, which is uploaded and maintained by the cluster and a private key that is kept private to the host that is running the SSH client. These keys authorize specific users to access the administration and service functions on the cluster. Each key is associated with a user-defined ID string that can consist of up to 40 characters. Up to 100 keys can be stored on the cluster. You can also add new IDs and keys or delete unwanted IDs and keys.

Secure Shell (SSH) is the communication vehicle between the host system you are using and either:

Authenticating SSH logins

When using AIX hosts, SSH logins are authenticated on the cluster using the RSA-based authentication supported in the OpenSSH client available for AIX. This scheme is based on public-key cryptography, using a scheme known commonly as RSA.

Note:Note: The authentication process for non-AIX hosts systems is similiar.

With this scheme (as in similar OpenSSH systems on other host types) the encryption and decryption is done using separate keys. This means it is not possible to derive the decryption key from the encryption key.

Physical possession of the private key allows access to the cluster, so it must be kept in a protected place, such as the .ssh directory on the AIX host, with restricted access permissions.

When an SSH client (A) attempts to connect to an SSH server (B), the key pair is needed to authenticate the connection. The key consists of two halves: the public and private keys. The SSH client public key is put onto the SSH Server (B) using some means outside of the SSH session. When the SSH client (A) tries to connect, the private key on the SSH client (A) is able to authenticate with its public half on the SSH server (B).

Running the command-line interface (CLI)

In order to use the command-line interface (CLI) or SAN Volume Controller Console system you must have an SSH client installed on that system and perform the following tasks:

The master console has the SSH client software called PuTTY preinstalled. This software provides the Secure Shell (SSH) client function for users logged into the master console who wish to invoke the SAN Volume Controller command-line interface (CLI).

If you wish to run the SAN Volume Controller command-line interface (CLI) from a different system than the master console, you must install an SSH client. For your convenience, the installation program to install the PuTTY software on Windows can be found in the SSH client directory of the SAN Volume Controller Console CD-ROM. You can generate SSH public and private keys using the PuTTY software. You must store the SSH Client public key on all SAN Volume Controller clusters.

Connecting the SAN Volume Controller Console to additional clusters

The master console also has the SAN Volume Controller Console Web server and Common Information Model (CIM) Object Manager software preinstalled. This software depends on the PuTTY Secure Shell (SSH) client function for the SAN Volume Controller Console to programmatically access the SAN Volume Controller cluster. The master console comes with PuTTY SSH keys preinstalled. You can generate new PuTTY SSH keys unique to your master console and copy the private SSH key to the SAN Volume Controller Console directory and store the public SSH key on all clusters to which the SAN Volume Controller Console will connect.

You can also install the SAN Volume Controller Console on a Windows 2000 server system which you provide. If you intend to install the SAN Volume Controller Console on a host which you supply, you must install PuTTY first, which is a prerequisite for the SAN Volume Controller Console.

Related topics Concepts Storage Management Initiative Specification

(C) Copyright International Business Machines Corporation 2003, 2004