This chapter describes how to customize the SSH run-time environment
to meet your organization's specific security needs and
discusses the following topics:
Customizing
the User Environment on the SSH Client Host
Customizing the User Environment
on the SSH Server Host
Authentication
Customizing an Authenication
Method
When the TCP/IP configuration procedure is completed, all
req uired systemwide SSH configuration parameters are established.
The host is now prepared to become an SSH server by accepting remote connections,
and the SSH client is ready to execute SSH commands. Different environments
may have specific security requirements that can be achieved by
exercising control over SSH run-time parameters on two levels:
A systemwide
setup, which is typically the system manager's responsibility
and applies to running instances of the client and server processes.
A user-specific setup, which
is typicallythe responsibility of the account owner, from whose
account the SSH connections are made on the client host or to which
an SSH connection will be requested on the server host.
An important component of the SSH run-time environment is
the [.SSH2] subdirectory, created either by the user or automatically
by the SSH software, in the user's login directory (as
specified by SYS$LOGIN). SSH uses this subdirectory to store multiple
files needed for SSH to function. For example, if SYS$LOGIN is translated
into DKA0:[username], then this special subdirectory
would be DKA0:[username.SSH2]. Throughout this
manual, this directory is referred to as the [username.SSH2] directory.
HP TCP/IP Services for OpenVMS Guide to SSH
