Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Darren Tucker
November 5, 2005, 12:06 am
rate this thread
You're using OpenSSH? (looks like it but you don't say)
I suspect you corrupted the key while copying it into authorized_keys.
Depending on exactly how it was corrupted, earlier versions of OpenSSH
didn't handle that well and would abort the connection. This has been
fixed for a while.
You can prevent you client from trying public-key authentication
which will probably let you log in ok. For OpenSSH, this is
"ssh -oPreferredAuthentications=password yourserver" (or possibly
keyboard-interactive instead of password). For other clients it will
probably be different.
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
- » www.vivepc.com Tu tienda de ordenadores discos duros impresoras memorias, Lo + barato . 2Q...
- — Previous thread in » Secure Shell Forum
- » protocol question - issue with exit-status inside unfinished data stream?
- — Newest thread in » Secure Shell Forum