自动安装密钥交换以允许无密码身份validation（通过SSH）

• 我的系统/产品由两块电路板组成，它们直接连在一起，然后其中一块连接到第三个Windowsdebugging机器上（通过SSH进行连接，因为它们的电路板没有问题）
• 我有一个Linux发行版的自动安装脚本（RHEL 5.3）
• 用户将一次安装一块电路板，两块电路板都应该可以在另一块电路板上进行configuration/安装
• 我想完成安装，以便在两个板之间build立无密码的SSH连接

我以为我是成功的

1. 创build密钥（不/空密码）
   • ssh-keygen -t rsa
2. 将自己的公钥添加/复制到authorized_keys中
   • cat ~/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys
3. SSH到其他主机将关键字添加到known_hosts文件
   • ssh -o StrictHostKeyChecking=no 192.168.0.2 exit （Im .1）
4. 将这个.ssh/*文件复制到安装介质上，并将安装脚本复制到电路板（两个电路板，一次一个）
5. 然后可以从另一个ssh到每个板

但它抱怨RSA密钥不同，我应该更新known_hosts。

 # ssh 192.168.0.2 -vv OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.168.0.2 [192.168.0.2] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug2: key_type_from_name: unknown key type '-----BEGIN' debug2: key_type_from_name: unknown key type '-----END' debug1: identity file /root/.ssh/id_rsa type 1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: loaded 3 keys debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3 debug1: match: OpenSSH_4.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.3 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,[email protected],zlib debug2: kex_parse_kexinit: none,[email protected],zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,[email protected] debug2: kex_parse_kexinit: none,[email protected] debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_init: found hmac-md5 debug1: kex: server->client aes128-cbc hmac-md5 none debug2: mac_init: found hmac-md5 debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug2: dh_gen_key: priv key bits set: 131/256 debug2: bits set: 490/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ 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 8d:b5:11:e2:fd:e9:1b:4d:a2:20:3f:22:87:90:10:45. Please contact your system administrator. Add correct host key in /root/.ssh/known_hosts to get rid of this message. Offending key in /root/.ssh/known_hosts:2 RSA host key for 192.168.0.2 has changed and you have requested strict checking. Host key verification failed. 

试着

 rm -f /root/.ssh/known_hosts ssh -o StrictHostKeyChecking=no 192.168.0.1 exit # (itself!) ssh -o StrictHostKeyChecking=no 192.168.0.2 exit # might not be live/up 

问题是，两个主机都必须上/活！

• 不断检查以确保php脚本正在运行
• unrealircd在启动时运行
• 在编译OpenSSH Debian Squeeze的时候，我总是收到OpenSSL Header Version找不到的错误
• 无法SSH到Ubuntu服务器
• 隧道SSH“客户端 – >防火墙 – >服务器1 – >服务器1.2”

 Warning: Permanently added '192.168.0.1' (RSA) to the list of known hosts. ssh: connect to host 192.168.0.2 port 22: No route to host 

我没有得到的是当我rm -f /root/.ssh/known_hosts并做了ssh ，它添加了一个新的密钥ID给known_hosts ，即使id_rsa.pub是相同的！？

 Host 192.168.0.* StrictHostKeyChecking no UserKnownHostsFile /dev/null