[SOLVED] Configuring ssh for a cluster of 12 computers for a single account
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Configuring ssh for a cluster of 12 computers for a single account
I've been using rsh and rlogin for many years on clusters (using RedHat 7 through FC6 OS). Currently, I am trying to configure a cluster with Fedora 14, and I noticed that the man pages mention that rsh/rlogin are deprecated and the ssh should be used instead.
The first quesion I have is: Are rsh/rlogin going to disappear at some point; leaving only ssh? The clusters I work on are on their own private network (unconnected to anything else), so I dont need ssh for security. However, if rsh/rlogin are going to disappear at some point, I'd like to switch over to ssh now.
I've done some research on ssh, and managed to get it working between two nodes on the cluster -- but it required a bit of user input to work (using ssh-keygen and ssh-copy-id). It appears I have to not only create a key on each account, but also register that key on each node I will be connecting to. That's a lot of work for setting up these 12 computers. And heaven forbid I am ever required to do it for more than 1 account!
Anyhow, I figured that their has to be a way to automate this process or at least speed it up a little. Any advice would be appreciated!
To use key-based authentication, you must load your public key into the file ~/.ssh/authorized_keys on each host in the pool. You can use the same keys on more than one host. Also, if you use an agent on your client, then you only need to enter the pass phrase once.
Host-based authentication also uses keys, but the authentication occurs at the host level. Of course it can be fine-tuned but, the basic set up is to allow ALL users from host X onto host Y via SSH if they have first logged into host X.
RSH should have been phased out in the 1990's and replaced completely by SSH since it is so insecure.