Re: Connection closed, no reason given

• Previous message: Darren Tucker: "Re: Receive Window"
• In reply to: jois.de.vivre_at_gmail.com: "Connection closed, no reason given"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: 5 Nov 2005 00:53:40 GMT

jois.de.vivre@gmail.com writes:

>Hi,

>I was trying to set up passwordless authentication via ssh from one
>machine to another. I generated the key pair on my local machine using

>ssh-keygen -t dsa

>I copied the entry from id_dsa.pub into the remote machine's
>.ssh/authorized_keys file and expected to be able to login without a
>problem. However, when I try and login now it simply says

>Connection closed by 192.168.1.108

>And I can't ssh into it anymore. I suspect the problem is in the
>authorized_keys file, how can I force it to not look in there without
>having to go to that machine and manually delete the entry?

So you have root access on the remote machine? Did you do this for all
accounts on the remote machine? Ie, log in as another user and then su to
root to fix stuff.

Anyway, what often happens is that line breaks are introduced by the editor
on placing the string into the authorized_keys file.

The other think is if you experimenting, leave one connection always open
so that you can recover. Otherwise you are in the hole you are in now--
unable to get in to fix anything. So go over to that machine, delete the
entry and then do things with a fallback position.

• Previous message: Darren Tucker: "Re: Receive Window"
• In reply to: jois.de.vivre_at_gmail.com: "Connection closed, no reason given"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]