How to fix ssh connection: POSSIBLE BREAK-IN ATTEMPT
Avoid inputting “yes” when encountering a “POSSIBLE BREAK-IN ATTEMPT” message.
Method 1: Add parameter StrictHostKeyChecking=no
ssh -o StrictHostKeyChecking=no root@192.168.1.100
Method 2: Modify /etc/ssh/ssh_config configuration
StrictHostKeyChecking no
In addition, to prevent such warnings from appearing POSSIBLE BREAK-IN ATTEMPT!
Address 192.168.0.101 maps to localhost, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
You can change the GSSAPIAuthentication yes
in the /etc/ssh/ssh_config
configuration file to:
GSSAPIAuthentication no
You can use the sed
stream editor to complete the modification:
sed -i 's/# StrictHostKeyChecking ask/StrictHostKeyChecking no/' /etc/ssh/ssh_config
sed -i 's/GSSAPIAuthentication yes/GSSAPIAuthentication no/' /etc/ssh/ssh_config
service sshd restart
Leave a message
Disclaimer
- Welcome to visit the knowledge base of SRE and DevOps!
- License under CC BY-NC 4.0
- Made with Material for MkDocs and improve writing by generative AI tools
- Copyright issue feedback me#imzye.com, replace # with @