linux ssh互信配置


ssh-copy-id -i .ssh/id_rsa.pub root@192.168.3.20


注意:

ssh-copy-id不是这样使用,如下

ssh-copy-id root@192.168.3.21

[root@centos5 ~]# ssh-copy-id root@195.168.43.135
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: ERROR: ssh: connect to host 195.168.43.135 port 22: Connection refused
[root@centos5 ~]# ssh-copy-id root@195.168.43.135
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: ERROR: ssh_exchange_identification: read: Connection reset by peer
NAME
     ssh-copy-id — use locally available keys to authorise logins on a remote machine
SYNOPSIS
     ssh-copy-id [-f] [-n] [-i [identity_file]] [-p port] [-o ssh_option] [user@]hostname
     ssh-copy-id -h | -?
EXAMPLES
     If you have already installed keys from one system on a lot of remote hosts, and you then create a new key, on a new
     client machine, say, it can be difficult to keep track of which systems on which you've installed the new key.  One way
     of dealing with this is to load both the new key and old key(s) into your ssh-agent(1).  Load the new key first, with‐
     out the -c option, then load one or more old keys into the agent, possibly by ssh-ing to the client machine that has
     that old key, using the -A option to allow agent forwarding:


           user@newclient$ ssh-add
           user@newclient$ ssh -A old.client
           user@oldl$ ssh-add -c
           ... prompt for pass-phrase ...
           user@old$ logoff
           user@newclient$ ssh someserver


     now, if the new key is installed on the server, you'll be allowed in unprompted, whereas if you only have the old
     key(s) enabled, you'll be asked for confirmation, which is your cue to log back out and run


           user@newclient$ ssh-copy-id -i someserver


     The reason you might want to specify the -i option in this case is to ensure that the comment on the installed key is
     the one from the .pub file, rather than just the filename that was loaded into you agent.  It also ensures that only
     the id you intended is installed, rather than all the keys that you have in your ssh-agent(1).  Of course, you can
     specify another id, or use the contents of the ssh-agent(1) as you prefer.


     Having mentioned ssh-add(1)'s -c option, you might consider using this whenever using agent forwarding to avoid your
     key being hijacked, but it is much better to instead use ssh(1)'s ProxyCommand and -W option, to bounce through remote
     servers while always doing direct end-to-end authentication. This way the middle hop(s) don't get access to your
     ssh-agent(1).  A web search for ‘ssh proxycommand nc’ should prove enlightening (N.B. the modern approach is to use the
     -W option, rather than nc(1)).

环境:

node1:192.168.3.20 
node2:192.168.3.21

用到的命令
  • ssh-keygen:创建公钥和密钥,会生成id_rsa和id_rsa.pub两个文件
  • ssh-copy-id:把本地的公钥复制到远程主机的authorized_keys文件(不会覆盖文件,是追加到文件末尾),并且会设置远程主机用户目录的.ssh和.ssh/authorized_keys权限 
    权限为: 
    chmod 700 ~/.ssh 
    chmod 600 ~/.ssh/authorized_keys

下面开始

1.在两台机器上生成各自的key文件

 [root@192.168.3.20]#ssh-keygen -t rsa       #下面一直按回车就好
 [root@192.168.3.21]#ssh-keygen -t rsa

2.用ssh-copy-id 把公钥复制到远程主机上,命令也要

[root@192.168.3.20]#ssh-copy-id -i  .ssh/id_rsa.pub root@192.168.3.21
[root@192.168.3.21]#ssh-copy-id -i  .ssh/id_rsa.pub root@192.168.3.20

注:如果不是默认的端口,可以这样写 
ssh-copy-id -i ~/.ssh/id_rsa.pub “-p 2022 root@192.168.3.21”

现在就可以直接登录了

[root@192.168.3.20]#ssh root@192.168.3.21,试试吧

说明:

  • 上面是以root用户配置互信,如果想要其它用户,可以切到相应的用户下执行命令即可
  • 如果单纯的只需要单向信任,在一台机器上执行命令就可以了,比如说node1连接node2,不用密码的话,在node1上执行命令就可以了
  • 3.也可以把ip地址和主机名对应关系加到 /etc/hosts里 这样直接ssh 主机名就可以了(eg:192.168.3.21 node2 加到hosts里就可以了

出处:https://blog.csdn.net/chenghuikai/article/details/52807074

阅读更多

没有更多推荐了,返回首页