4.-Copy etc/ssh/ssh_known_hosts in all the cluster nodes
5.- Create the /etc/ssh/shosts.equiv with the name of all the cluster nodes.
But, it doesn´t work, what can i do? Can anyone help me?
Regards,
Alicia Acero
----------------------------
Confidencialidad:
Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucción.
Disclaimer:
This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately.
----------------------------
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
03-30-2012, 09:26 PM
Cameron Simpson
Ssh passwordless configuration problem in RHEL 6.2
On 30Mar2012 15:17, Acero Fernandez Alicia <alicia.acero@ciemat.es> wrote:
| I have installed the following version of openssh in my cluster:
[...]
| openssh-5.3p1-70.el6.x86_64
| openssh-server-5.3p1-70.el6.x86_64
|
| I am trying to configure ssh to allow users to run mpi programs in my
| cluster, then I need to configure ssh properly.
|
| I have tried the following:
Are these things from some recipe somewhere? If so, its URL?
Do you _really_ want _all_ of these turned on?
You should decide on what basis users are permitted to run these
programs, and only turn on the relevant authentication.
| 4.-Copy etc/ssh/ssh_known_hosts in all the cluster nodes
Check its permissions. Ssh authenitcation and configuration files
generally need very restricted write permissions (only the owner) and
some of them need restricted read (eg private keys may not be readable
by other than the owner).
| 5.- Create the /etc/ssh/shosts.equiv with the name of all the cluster nodes.
|
| But, it doesn´t work, what can i do? Can anyone help me?
Do a test ssh. "tail -F /var/log/secure" on the target server while you
do so. It will report the reason access is refused. Then you will have a
better idea of what to look for.