Differences
This shows you the differences between the selected revisions of the page.
| 2008-08-22 | 2008-08-23 | ||
| das (213.161.4.49) (hidden) | Restored revision 1218522283. Undoing revisions 1219422350, 1219422381. (martin) (hidden) | ||
| Line 1: | Line 1: | ||
| ====== Common Error Messages ====== | ====== Common Error Messages ====== | ||
| - | sadasd | + | ===== [[host_key]] The server's host key was not found in the cache ===== |
| + | This error message occurs when WinSCP connects to a new [[SSH]] server. Every server identifies itself by means of a host key; once WinSCP knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine. | ||
| + | |||
| + | 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]]. | ||
| ===== WARNING - POTENTIAL SECURITY BREACH! ===== | ===== WARNING - POTENTIAL SECURITY BREACH! ===== | ||
| Line 78: | Line 85: | ||
| You will get the error while authenticating when: | You will get the error while authenticating when: | ||
| * You have entered incorrect password, used used non-authorized key, etc. | * You have entered incorrect password, used used non-authorized key, etc. | ||
| - | * The account you are trying to use cannot be logged in. This can be case even when you get "Access denied" only after entering password, as for security reasons, most SSH servers do not reveal information 312 | + | * The account you are trying to use cannot be logged in. This can be case even when you get "Access denied" only after entering password, as for security reasons, most SSH servers do not reveal information about the accounts. Reasons for not being allowed to login include: |
| + | * The account (username) you have entered on Login dialog does not exist at all. | ||
| + | * The account is disabled. | ||
| + | * The password has expired. | ||
| * Number of parallel sessions allowed for the account has been exceeded. | * Number of parallel sessions allowed for the account has been exceeded. | ||
| * You are trying to connect with super-user account (''root''), without having allowed that. Please read [[faq_su|FAQ]]. | * You are trying to connect with super-user account (''root''), without having allowed that. Please read [[faq_su|FAQ]]. | ||
| Line 135: | Line 145: | ||
| You can also try to run the respective command from terminal (with the same account that you use with WinSCP), to verify that you can execute it. You may not have sufficient permissions, or the command dependencies may not be installed. | You can also try to run the respective command from terminal (with the same account that you use with WinSCP), to verify that you can execute it. You may not have sufficient permissions, or the command dependencies may not be installed. | ||
| - | |||
| ===== Invalid access to memory ===== | ===== Invalid access to memory ===== | ||