问题原文
原帖链接 · spuder · CC BY-SA 3.0
Each user creates and destroys 15+ VM's per day. The VM's are created in the company's internal OpenStack cloud.
Every time a new vm is assigned an ip address which has previously been handed out, the user gets the dreaded host key verification failed error. This is because the ssh key does not match the IP address in the users known_hosts file.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
xxxxxxxxxxx
Please contact your system administrator.
Add correct host key in /home/user/.ssh/known_hosts to get rid of this message.
Offending key in /home/user/.ssh/known_hosts:4
RSA host key for domain.com has changed and you have requested strict checking.
Host key verification failed.
The two solutions I can see are:
- Turn off strict checking - (Security risk)
- Have the users run
ssh-keygen -RipAddress- (users are getting tired of this solution, since then run into it multiple times per day)
Is there any way to prevent this error message, yet stay secure? perhaps turn off security checking for just a specific subnet?
已采纳解答
原帖链接 · Hauke Laging · CC BY-SA 3.0
The great feature HostKeyAlias solves your problem:
ssh -o HostKeyAlias=hostkeyalias__vm_2013-05-11_07 user@host
creates an entry hostkeyalias__vm_2013-05-11_07 (without IP) in known_hosts. Of course, you could write a script or shell function which sets this value before each ssh call. Or you use a shell variable:
HOSTKEYALIAS=hostkeyalias__vm_2013-05-11_07
ssh -o HostKeyAlias=$HOSTKEYALIAS user@host
and change $HOSTKEYALIAS whenever the VM is changed. From time to time the old entries should be deleted from known_hosts.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
