Timeline for ECDSA host key for my IP has changed - why?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2023 at 11:10 | history | edited | Stéphane Chazelas | CC BY-SA 4.0 |
added 44 characters in body
|
| Dec 19, 2020 at 21:12 | comment | added | Ken | From the machine where I got the error, I just accessed the server through SFTP (Nautilus). It failed once, then it connected but did not ask me to accept a new key (as it does when I access a server for the first time) | |
| Dec 19, 2020 at 21:05 | comment | added | Ken | Thank you. I am confused though. Am I worried about the server or my local machine? | |
| Dec 19, 2020 at 20:59 | comment | added | Michael Homer | I don't know what is happening, I was just completing the list. The point of the host key check is to detect MITM, so other services appearing to function normally is not a major data point as those can be proxied (though SFTP is still over SSH, of course). | |
| Dec 19, 2020 at 20:53 | comment | added | Ken | Do you mean, when I go through SSH? I have services running on my machine that are performing normally. I can access that machine through SFTP or Webmin, etc I see @MichaelHomer you are adding a fourth option... | |
| Dec 19, 2020 at 20:53 | comment | added | Michael Homer | 4. You're actually connecting to a different host than you thought. | |
| Dec 19, 2020 at 20:48 | comment | added | Ken | I have done none of those things. This machine (a DigitalOcean droplet running Ubuntu) is identical to another one and I keep both up-to-date. The other one has not exhibited this problem. If there was an update to SSH in the last few days - don't recall one - could that have triggered this? | |
| Dec 19, 2020 at 20:26 | history | answered | Bruce Malaudzi | CC BY-SA 4.0 |