ssh (client) stops working after upgrade to Feisty

[Matthew East]

Binary package hint: openssh-client

I just did an upgrade to Feisty, and I can't login to any servers via ssh. I don't receive an error message, it just does nothing.

Please let me know how I can contribute some debugging information!

Matt

[Matthew East (mdke)]

Someone confirmed this bug for me by email after I posted on the forum about it. He has shed some more light on potential sources:

</quote>
Hello,

http://ubuntuforums.org/showthread.php?t=319971
I had the problem too

Feisty up to date
It bugged me if I tried a host which I have never connected before
(asking to add the host to known_hosts) but never asked for a password
and hangs forever

After removing all packages with "askpass" in the name, it asked me my
password on the console.

I suppose it has to do with seahorse or ssh-agent vs seahorse-agent
playing bad together

I'm not registered on the forum. But if it works for you, could you
please add a comment in the bug report so to give a general direction
to how to find the root of the bug.

Bye

Stephane Loeuillet
</quote>

[Matthew East (mdke)]

Moving this task to seahorse since uninstalling that package has now resolved the problem. I suppose it could be something to do with gnome-keyring-daemon, not sure. Please let me know if I can debug further.

[Emmanuel Pacaud (emmanuel-pacaud)]

I've encoutered this issue and fixed it by removing the seahorse-daemon launch entry in gnome-session properties (System->preferences->session), without uninstalling seahorse.

Everything works fine now.

[Colin Watson (cjwatson)]

I tried to reproduce this and couldn't. Could you use the -vvv option to ssh and post the debugging output here?

[Matthew East (mdke)]

Sure, below is the output. Did you try installing seahorse and running "seahorse-daemon" before trying to reproduce?

matt@kalliope:~$ ssh -vvv eustathios
OpenSSH_4.3p2 Debian-7ubuntu1, OpenSSL 0.9.8c 05 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to eustathios [192.168.2.3] port 22.
debug1: Connection established.
debug1: identity file /home/matt/.ssh/identity type -1
debug1: identity file /home/matt/.ssh/id_rsa type -1
debug3: Not a RSA1 key file /home/matt/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /home/matt/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.2p1 Debian-7ubuntu3
debug1: match: OpenSSH_4.2p1 Debian-7ubuntu3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-7ubuntu1
debug2: fd 3 setting O_NONBLOCK
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
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,<email address hidden>,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,<email address hidden>,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,<email address hidden>,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,<email address hidden>,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,<email address hidden>,zlib
debug2: kex_parse_kexinit: none,<email address hidden>,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2:...

[Sebastian Dröge (slomo)]

This is fixed now in feisty with 0.9.9-0ubuntu2

[Matthew East (mdke)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Sebastian Dröge:
> This is fixed now in feisty with 0.9.9-0ubuntu2

Thanks Sebastian!!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFiFbMtSaF0w5rBv8RAoYGAJ9s7Fz05d5XRz4PnlO8RAEjMN+6vwCff96Z
9iROkCItWl4FhWnlZrQNhgc=
=IFv4
-----END PGP SIGNATURE-----

[Peter Magnusson (kmpm)]

I have the same error with 0.9.10-0ubuntu2.
I won't attach any output because it's almost exactly the same as above.

[Arun (arunmarjun)]

I had the same problem, uninstalling seahorse fixed it. Boy, I was trying to figure out what was going on. A wierd thing happened which I thought might help. when I login to kde and try ssh'ing i got a dialog box asking for my ssh passphrase with an option to store it in my keyring. I entered my passphrase it brought me to the login on the konsole. I was able to successfully log in. I logged out and tried to ssh again..no dialog this time and it just hangs then on when I try to ssh anywhere

[Rory McCann (rorymcc)]

I have the same error with seahorse 1.0.1-0ubuntu1. Logging out and logging in again 'fixed' it.