ssh_keysign: no reply - key_sign failed
When trying to run FLUENT in network parallel using ssh you receive the following error:
ssh_keysign: no reply
Resolution/Workaround 1 : If you are using Host Based Authentication this will not work at this time. The workaround is to use the User Public Key Based Authentication for passwordless ssh. We are investigating this issue related to host based authentication for passwordless ssh.
Resolution 2 : Check that the "setuid root" is not set on certain executables. Upgrading to the latest ssh could also correct this issue. A useful FAQ on SSH is <a target=_blank href="http://www.snailbook.com/faq/trusted-host-howto.auto.html">http://www.snailbook.com/faq/trusted-host-howto.auto.html</a>http://www.snailbook.com/faq/trusted-host-howto.auto.html
Configuring the ssh Client
The secure shell client ( ssh ), is a more secure alternative to rsh and is also used widely. Depending on the specific protocol and the version deployed, configuration involves a few steps. SSH1 and SSH2 are two current protocols. OpenSSH is an open implementation of the SSH2 protocol and is backwards compatible with the SSH1 protocol. To add a client machine, with respect to user configuration, the following steps are involved:
Generate a public-private key pair using ssh-keygen (or using a graphical user interface client). For example: ssh-keygen -t dsa where it creates a Digital Signature Authority (DSA) type key pair.
Place your public key on the remote host.
For SSH1 , insert the contents of the client ( ~/.ssh/identity.pub ) into the server ( ~/.ssh/authorized_keys ).
For SSH2 , insert the contents of the client ( ~/.ssh/id_dsa.pub ) into the server ( ~/.ssh/authorized_keys2 ).
The client machine is now added to the access list and the user is no longer required to type in a password each time. For additional information, consult your system administrator or refer to your system documentation.