Warning: Remote Host Identification Has Changed!

happy

Well-Known Member
ja, genau dieses problem habe ich af meinem Proxy server für ssh.
Folgdes: habe netcat als eine art proxy auf einem server eingesetzt, den ich als meinem ssh proxy nutzen möchte.
wenn ich .
Code:
ssh happy@proxy -p2001
mache funzt wunderbar , ich speichere einfach den key in known_hosts
aber wenn ich zu andem server uber den proxy connten will.
Code:
ssh happy@141.44.198.20 -p2002
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the DSA host key has just been changed.
The fingerprint for the DSA key sent by the remote host is
d2:97:6a:ea:fe:60:91:95:a2:fc:aa:0a:32:85:1c:b2.
Please contact your system administrator.
Add correct host key in /home/happy/.ssh/known_hosts to get rid of this message.
Offending key in /home/happy/.ssh/known_hosts:1
DSA host key for 141.44.198.20 has changed and you have requested strict checking.
Host key verification failed.
Klar könnte man jetzt in der /home/happy/.ssh/known_hosts die zeile mit der 141.44... rauslöschen, doch ich habe viel mehr shells.
was kann ich machen umd nich jedes mal den schlössel aus der knwon_host rauslöschen zu müssen?
 
DSA host key for 141.44.198.20 has changed and you have requested strict checking.
Schalte strict checking ab....
Code:
     StrictHostKeyChecking
             If this flag is set to ``yes'', ssh will never automatically add
             host keys to the $HOME/.ssh/known_hosts file, and refuses to con-
             nect to hosts whose host key has changed.  This provides maximum
             protection against trojan horse attacks, however, can be annoying
             when the /etc/ssh/ssh_known_hosts file is poorly maintained, or
             connections to new hosts are frequently made.  This option forces
             the user to manually add all new hosts.  If this flag is set to
             ``no'', ssh will automatically add new host keys to the user
             known hosts files.  If this flag is set to ``ask'', new host keys
             will be added to the user known host files only after the user
             has confirmed that is what they really want to do, and ssh will
             refuse to connect to hosts whose host key has changed.  The host
             keys of known hosts will be verified automatically in all cases.
             The argument must be ``yes'', ``no'' or ``ask''.  The default is
             ``ask''.
 
Back
Top