ssh connection batch modify the hostname reported the following tips:
[root@bqh-nfs-123 ~]# vim modfilyhostname.sh [root@bqh-nfs-123 ~]# sh modfilyhostname.sh Address 192.168.43.117 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Address 192.168.43.118 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! to the address - POSSIBLE BREAK-IN ATTEMPT! Address 192.168.43.119 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! to the address - POSSIBLE BREAK-IN ATTEMPT! Address 192.168.43.120 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! to the address - POSSIBLE BREAK-IN ATTEMPT! Address 192.168.43.121 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! to the address - POSSIBLE BREAK-IN ATTEMPT! Address 192.168.43.122 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! to the address - POSSIBLE BREAK-IN ATTEMPT! Address 192.168.43.123 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! to the address - POSSIBLE BREAK-IN ATTEMPT! Address 192.168.43.124 maps to bogon, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Generally no login password when configuring the cause, the solution is as follows:
Modify the machine ssh_config file , the GSSAPIAuthentication yse read: GSSAPIAuthentication NO
[root@bqh-117 ~]# sed -i 's#GSSAPIAuthentication yes#GSSAPIAuthentication no#g' /etc/ssh/ssh_config [root@bqh-117 ~]# sed -n 50p /etc/ssh/ssh_config GSSAPIAuthentication no
The role of GSSAPIAuthentication: whether to allow the use of user authentication based on GSSAPI