Differences between version 13 and predecessor to the previous major change of SSHErrors.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 13 | Last edited on Tuesday, May 24, 2005 10:55:37 am | by IanMcDonald | Revert |
| Older page: | version 12 | Last edited on Friday, December 3, 2004 10:24:33 pm | by JohnMcPherson | Revert |
@@ -49,8 +49,12 @@
You can solve this problem by either installing a [SSH] client which supports protocol version 2 on the source machine (strongly recommended), or by changing the configuration of the [SSH] server on the destination machine. Note that protocol versions 1.x are deprecated because they're vulnerable. You should really upgrade the client instead.
If you cannot do that for whatever reason, you have to permit clients to use a 1.x protocol in sessions with the server by changing the directive <tt>Protocol 2</tt> to <tt>Protocol 2,1</tt> in the server's <tt>/etc/ssh/sshd_config</tt>. Don't forget to restart the daemon.
+
+!!! Permission denied errors
+
+If you get an error similar to <tt>Permission denied (publickey).</tt> you probably have not put your public key into the authorized_keys file in ~/.ssh or else you may have corrupted that file.
----
Part of CategorySecurity, CategoryNetworking, CategoryErrors
