Morgan - I did set the server keys to be the same. I still received the error. I assumed this was the case because the IP address that was connected to was different. I will double check my method for changing the keys, and let you know. ----- Original Message ----- From: "Morgan A. Miskell" <[EMAIL PROTECTED]> To: "Christopher Crowley" <[EMAIL PROTECTED]> Sent: Thursday, August 16, 2001 3:28 PM Subject: RE: SSH Server configuration for a multi-node system. > Easiest way is to use the same server key pairs on all four machines, that > way no matter which one they hit, it has the same keys and you don't get > that error.....not a great security policy, but it works! > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > > Christopher Crowley > > Sent: Thursday, August 16, 2001 3:48 PM > > To: [EMAIL PROTECTED] > > Subject: SSH Server configuration for a multi-node system. > > > > > > Hello - > > > > Any suggestions for overcoming this problem: > > > > I use DNS to round-robin a server ( rscluster.tulane.edu ) with four > > nodes. When a user attempts to SSH to this machine, the SSH client would > > give them a warning > > @ WARNING: HOST IDENTIFICATION HAS CHANGED! @ > > in 3 out of 4 cases. > > > > I would like to implement a ssh only policy for connecting to > > this machine. > > There are a lot > > of users (1000) who currently telnet to this system from their PCs. So, I > > cannot manage known_host_keys centrally. > > > > Thanks in advance, > > Chris > > > > > > > > > >
