HP OpenVMS Systems Documentation

Content starts here

Running the TCPIP$CONFIG Configuration Command Procedure

  Table of Contents

  Glossary

  Index

After TCP/IP installation is complete, the SSH service must be configured using the TCP/IP configuration command procedure, TCPIP$CONFIG.COM. The configuration procedure creates the systemwide SSH environment by setting up various components of SSH, such as configuration files and host keys.

Once you complete the client and server configuration using TCPIP$CONFIG, you can customize the configuration with parameters to meet the needs of your specific run-time environment. For more information about customizing your run-time environment, see Chapter 3. For general configuration procedures, refer to the HP TCP/IP Services for OpenVMS Installation and Configuration manual.

To run the configuration command procedure, follow these steps:

  1. Invoke the TCPIP$CONFIG configuration command procedure. The main Configuration menu is displayed:

    $ @ SYS$STARTUP:TCPIP$CONFIG.COM
     TCP/IP Network Configuration Procedure
    
            This procedure helps you define the parameters required
            to run HP TCP/IP Services for OpenVMS on this system.
    
    
            Checking TCP/IP Services for OpenVMS configuration database files.
    
    
    
    
            HP TCP/IP Services for OpenVMS Configuration Menu
    
            Configuration options:
    
                     1  -  Core environment
                     2  -  Client components
                     3  -  Server components
                     4  -  Optional components
    
                     5  -  Shutdown HP TCP/IP Services for OpenVMS
                     6  -  Startup HP TCP/IP Services for OpenVMS
                     7  -  Run tests
    
                     A  -  Configure options 1 - 4
                    [E] -  Exit configuration procedure
    
    Enter configuration option:
  2. Choose option 2 (Client components) to configure the SSH client.

  3. Choose option 3 (Server components) to configure the SSH server. .

During the configuration procedure, TCPIP$CONFIG creates the systemwide environment necessary to run the SSH client and server, including:

  • The SSH server account TCPIP$SSH, and the account's default directory, TCPIP$SSH_DEVICE:[TCPIP$SSH]. Note that the default device of the account is defined by the logical name TCPIP$SSH_DEVICE. This logical name can be assigned by the system manager. If this logical name is not defined, the default name is SYS$SYSDEVICE.

  • All subdirectories and files required by the SSH server.

In addition, the configuration procedure copies all the necessary files from the distribution kit into the appropriate directories. Table 2-1 lists the files that are created during the configuration of the SSH server and SSH client.

Table 2-1 Files and Directories Created During SSH Configuration

Directory on TCPIP$SSH_DEVICE:File NameDescriptionServer/ Client
[TCPIP$SSH.SSH2]SSH2_CONFIG.

Configuration file

Client

[TCPIP$SSH.SSH2]SSHD2_CONFIG.

Configuration file

Server

(and client for host-based authen- tication)

[TCPIP$SSH.SSH2]SHOSTS.EQUIV

Contains a list of trusted hosts, used by the host-based authentication method.

Server

[TCPIP$SSH.SSH2]

HOSTKEY.

HOSTKEY.PUB

Contains private (HOSTKEY) and public (HOSTKEY.PUB) server host keys.

Server

[TCPIP$SSH.SSH2]

RANDOM_SEED.

Contains random numbers for cryptographics operations.

Server

[TCPIP$SSH.SSH2.KNOWNHOSTS] 

Contains public keys of all remote client hosts that may attempt to connect to the server using host-based authentication.

Server

[TCPIP$SSH.SSH2.HOSTKEYS]

Contains host keys for all remote servers to which the user connects using the SSH client.

Client