Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.
To make the host-based authentication more secure, you may want to consider the following optional configuration settings:
With the AllowSHosts and DenySHosts keywords in the sshd2_config file you can filter the .shosts, .rhosts, /etc/hosts.equiv and /etc/shosts.equiv entries.
If you want to allow only global configuration files (/etc/hosts.equiv and /etc/shosts.equiv), make sure that you have the following entry in your sshd2_config file:
After this modification the .shosts and .rhosts files will not be used in host-based authentication.
To force an exact match between the hostname that the client sends to the server and the client's DNS entry, make sure that you have the following definition in your /etc/ssh2/sshd2_config file:
In this case, make sure the /etc/hosts file has the fully qualified hostname listed before the short hostname, for example:
126.96.36.199 client.example.com client
Even if you are not using /etc/hosts as your primary resolver, you may need to add entries to it for the client and the server to allow them to resolve each other's fully qualified domain names (if they are not able to do so otherwise).
Please note that when HostbasedAuthForceClientHostnameDNSMatch is used, host-based authentication through NAT (Network Address Translation) will not work.