Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

how to automate public key authentication when server dual-boots two li

Subject: how to automate public key authentication when server dual-boots two linuxes
Date: Wed, 07 Jun 2006 12:03:37 -0400
I have a hopefully simple question on setup for sshd.

I recently switched my server from rshd to sshd and it works fine. I am using public key authentication.

However the wrinkle is that this server has two different linux partitions which I need to alternate between (strictly only one at a time, not a virtual machine setup). With rshd they both appeared to be identical as far as rsh authentication. With sshd, when I booted the second one, and then tried an ssh to it from another machine, of course I got

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
 ... rsa fingerprint ...   etc etc.

I realize that this is exactly what sshd is designed to do, to detact impersonation of the server, but unfortunately that's exactly what I need to do (but of course don't want any other impersonator to be recognized).

I could try just overwriting the second server partition's
/usr/local/etc/ssh_host_rsa_key.pub
with the first one - but is that the right way? Would that cause other problems? Hoping someone else has come across this and there is some recognized solution to this.


John


<Prev in Thread] Current Thread [Next in Thread>