can't ssh out?

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Mon Apr 9 18:06:38 UTC 2007


On Mon, Apr 09, 2007 at 01:53:34PM -0400, Matt Price wrote:
> ho folks,
> 
> on an otherwise functioning laptop, I've suddenly found I can't ssh out,
> although, fortunately, I can ssh IN, so my data's not entirely trapped.
> I've tried from various user accounts, including one fresh one, so the
> problem doesn't seem to be in the ~/.ssh/ directory.  
> 
> ssh -v [host] gives this:
> 
> ~$ ssh -v 192.168.2.210
> OpenSSH_4.3p2 Debian-8ubuntu1, OpenSSL 0.9.8c 05 Sep 2006
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Applying options for 192.*
> debug1: Applying options for *
> debug1: Connecting to 192.168.2.210 [192.168.2.210] port 22.
> debug1: Connection established.
> debug1: identity file /home/matt/.ssh/identity type -1
> debug1: identity file /home/matt/.ssh/id_rsa type -1
> debug1: identity file /home/matt/.ssh/id_dsa type -1
> debug1: Remote protocol version 2.0, remote software version
> OpenSSH_4.3p2 Debian-7ubuntu1
> debug1: match: OpenSSH_4.3p2 Debian-7ubuntu1 pat OpenSSH*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-8ubuntu1
> debug1: An invalid name was supplied
> Configuration file does not specify default realm
> 
> debug1: An invalid name was supplied
> A parameter was malformed
> Validation error
> 
> debug1: An invalid name was supplied
> Configuration file does not specify default realm
> 
> debug1: An invalid name was supplied
> A parameter was malformed
> Validation error
> 
> debug1: SSH2_MSG_KEXINIT sent
> debug1: SSH2_MSG_KEXINIT received
> debug1: kex: server->client aes128-cbc hmac-md5 none
> debug1: kex: client->server aes128-cbc hmac-md5 none
> debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
> debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
> debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
> debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
> Warning: Permanently added '192.168.2.210' (RSA) to the list of known
> hosts.
> debug1: ssh_rsa_verify: signature correct
> debug1: SSH2_MSG_NEWKEYS sent
> debug1: expecting SSH2_MSG_NEWKEYS
> debug1: SSH2_MSG_NEWKEYS received
> debug1: SSH2_MSG_SERVICE_REQUEST sent
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> ------------------------------
> ...after this the process just hangs.  Meanwhile on the server side I
> get this in /var/log/auth.log:
> sshd[PID]: fatal: Timeout before authentication for 192.168.2.104
> 
> I'm not sure what the trouble can be.  As I mentioned, the process works
> fine in the opposite direction so there's no issue with the network
> connection, and i don't believe i've modified the files in /etc/ssh/ for
> a while -- certainly not recently enough to have caused this problem
> directly.  I am running ubuntu feisty, so this may be a bug in ssh, but
> i don't seem anything reported on launchpad and this is pretty odd
> behaviour.  So I just wondered if there was an ssh guru out there who
> could help me interpret these messages.  

Any chance of an error in /etc/ssh/ssh_config ?

Or perhaps a corrupted file in ~/.ssh/

Does it affect all users on the system or just some?

--
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list