Differences
This shows you the differences between the selected revisions of the page.
| 2012-09-20 | 2012-09-20 | ||
| no summary (24.184.182.77) (hidden) | Restored revision 1347778294. Undoing revision 1348139300. (Petr) (hidden) | ||
| Line 10: | Line 10: | ||
| - | fuck you | + | |
| + | If you see this message, it means that WinSCP has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other means, such as asking the machine's administrator. | ||
| + | |||
| + | If you see this message and you know that your installation of WinSCP has connected to the same server before, it may have been recently upgraded to SSH protocol version 2. SSH protocols 1 and 2 use separate host keys, so when you first use SSH-2 with a server you have only used SSH-1 with before, you will see this message again. You should verify the correctness of the key as before. ((&puttydoccite)) | ||
| + | |||
| + | Read more about [[ssh#verifying_the_host_key|verifying host keys]]. | ||
| + | |||
| + | |||
| + | Learn also how to [[scripting#hostkey|accept host key automatically in script]]. | ||
| + | |||
| + | ===== [[security_breach]] Warning - Potential security breach! ===== | ||
| + | This message, followed by "The server's host key does not match the one WinSCP has is cache", means that WinSCP has connected to the SSH server before, knows what its host key should be, but has found a different one. | ||
| This may mean that a malicious attacker has replaced your server with a different one, or has redirected your network connection to their own machine. On the other hand, it may simply mean that the administrator of your server has accidentally changed the key while upgrading the SSH software; this shouldn't happen but it is unfortunately possible. | This may mean that a malicious attacker has replaced your server with a different one, or has redirected your network connection to their own machine. On the other hand, it may simply mean that the administrator of your server has accidentally changed the key while upgrading the SSH software; this shouldn't happen but it is unfortunately possible. | ||