[Contents] [Index]

About This Document >>     Installing SSH Tectia Server for IBM z/OS >>     Using SSH Tectia Server for IBM z/OS >>     Configuring the Server >>     Configuring the Client >>     Authentication >>         Server Authentication with Public Keys >>         User Authentication with Passwords         User Authentication with Public Keys >>         Host-Based User Authentication >>             Client Configuration             Server Configuration             Optional Configuration Settings         User Authentication with Keyboard-Interactive >>     Troubleshooting SSH Tectia Server for IBM z/OS >>     Examples of Use >>     Man Pages >>     Log Messages >>

Client Configuration

To enable host-based authentication with traditional public keys on the client, do the following steps as ClientUser:

1. Generate a host key. By default, /etc/ssh2/hostkey and /etc/ssh2/hostkey.pub are generated during installation, so you can skip this step. Otherwise, give the following command:

   > /usr/lpp/ssh2/bin/ssh-keygen2 -P /etc/ssh2/hostkey
   

2. Add the following line in the /etc/ssh2/ssh2_config file:

   AllowedAuthentications hostbased

   Also other authentication methods can be listed. Place the least interactive method first. For example:

   AllowedAuthentications hostbased,publickey,password

3. Change the DefaultDomain keyword in the ssh2_config file to reflect your fully qualified domain:

   DefaultDomain example.com

   Setting this is mandatory if the HostbasedAuthForceClientHostnameDNSMatch keyword in the sshd2_config file on Server has been set to yes. But even if HostbasedAuthForceClientHostnameDNSMatch is not used, the DefaultDomain keyword is useful, for example, on AIX and Solaris, which report only the short hostname by default.