| 83 | | |
| 84 | | When things go wrong |
| 85 | | server key changed |
| 86 | | If you see something like |
| 87 | | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
| 88 | | @ WARNING: HOST IDENTIFICATION HAS CHANGED! @ |
| 89 | | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
| 90 | | IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! |
| 91 | | Someone could be eavesdropping on you right now (man-in-the-middle attack)! |
| 92 | | It is also possible that the host key has just been changed. |
| 93 | | Please contact your system administrator. |
| 94 | | Add correct host key in /home/usernme/.ssh/known_hosts to get rid of this |
| 95 | | message. Agent forwarding is disabled to avoid attacks by corrupted servers. |
| 96 | | X11 forwarding is disabled to avoid attacks by corrupted servers. |
| 97 | | This indicates that the host public key that your client believes is valid |
| 98 | | for the server you're trying to connect to doesn't match the host key that |
| 99 | | the server is using. As the message indicates, it either means someone is |
| 100 | | trying to subvert your connection, or that a system administrator has for |
| 101 | | some reason changed the host key for the server. You should at this point contact |
| 102 | | the administrator of the server in question to find out what is happening. |
| 103 | | server key not yet known If you see something like Host key not found |
| 104 | | from the list of known hosts. Are you sure you want to continue connecting (yes/no)? |
| 105 | | this just means that your client doesn't yet know a host key for the server |
| 106 | | you're connecting to. If you believe it is unlikely that anyone is going to choose |
| 107 | | precisely this time to attempt to intercept and spoof your attempt to connect to the |
| 108 | | server in question, then saying yes at this point will result in the server host public |
| 109 | | key being added to your (but not the client machine's) list of known hosts. |
| 110 | | ssh or sftp connection is closed by remote site after 30-60 minutes |
| 111 | | Some sites run a version of ssh that periodically forces another run of the |
| 112 | | key-exchange phase, and this attempt to rekey kills the connection from Sun's SSH. |
| 113 | | You may get a message such as: |
| 114 | | dispatch protocol error: type 20 plen 140 |
| 115 | | If you run into this problem, which may prevent you from transferring large files, |
| 116 | | try using the OpenSSH client (openssh or opensftp), as the |
| 117 | | rekeying message is not sent to OpenSSH clients. |
| 118 | | anything else If you find any other misfeatures in the installed |
| 119 | | ssh programs please contact helpdesk, giving as much detail as possible. |
