I have good a problem with connection via ssh, i dont know what should i do
C:\Users\jel>ssh pi@172.20.10.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:jmfQ+bwBowCldMsTDtG9jFY+gflsjf2kBs1pUZKpw8Q.
Please contact your system administrator.
Add correct host key in C:\\Users\\jel/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in C:\\Users\\jel/.ssh/known_hosts:10
ECDSA host key for 172.20.10.2 has changed and you have requested strict checking.
Host key verification failed.
i dont know what should i do
There are many options.... The choice is up to you.
You could disable Strict Checking
You could modify Key #10 in C:\\Users\\jel/.ssh/known_hosts to be SHA256:jmfQ+bwBowCldMsTDtG9jFY+gflsjf2kBs1pUZKpw8Q.
You could delete Key #10 from C:\\Users\\jel/.ssh/known_hosts
You could delete all the content of C:\\Users\\jel/.ssh/known_hosts
The underlying problem that ssh is alerting you to is almost certainly that you have installed a fresh Operating System on the RPi identified as 172.20.10.2 since the last time you made an ssh connection to it from your Windows workstation.
Since your RPi at 172.20.10.2 is unlikely to be accessible from the global Internet (unless you have enabled Port Forwarding in your Internet Router) then any risk that "SOMEONE IS DOING SOMETHING NASTY!" will be limited to other machines and users on your own local network.
Statistics: Posted by B.Goode — Wed Apr 10, 2024 5:06 pm
