I have established secure shell (SSH) connectivity on my cluster where each node has a public key. However, when I use any secure shell utility on the cluster, I am still prompted for a password. What am I doing wrong?
Assuming that you have set up a NULL “ passphrase” for your login account when using the ssh-keygen utility, for all systems in your cluster, and that you have distributed the public key for each node to all the other nodes (i.e., the public keys reside in the “ ~/.ssh/authorized_keys” file), then check the permissions of your home directory on your cluster. The “group” and “other” permission categories should only have read and execute accessibility for the home directory folder. If you activate a “write” permission setting for either the “group” or “other” categories, SSH will prompt you for the password. Also, the “ ~/.ssh” subdirectory should only have read, write, and execute permission for the login owner.
Note that the expect shell script sshconnectivity.exp will remove the write access capability on the group and other “permission categories” for the user’s home directory folder.
Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.
Notice revision #20110804