Excuse me Chuck but the problem is clear.
When you do
ssh -v SERVER.DOMAIN
you obtain an output similar to the following:
"
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to wall [141.250.199.62] port 22.
debug1: Connection established.
debug1: identity file /home/marcop/.ssh/identity type -1
debug1: identity file /home/marcop/.ssh/id_rsa type -1
debug1: identity file /home/marcop/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2
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
debug1: Host 'wall' is known and matches the RSA host key.
debug1: Found key in /home/marcop/.ssh/known_hosts:87
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
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
There is no crash and no way to report it via apport.
I don't know what "Unspecified GSS failure" means. I have no kerberos system installed in my network (maybe could be this?).
However my problem was related to the fact that connecting to a server via ssh, apart from displaying the error indicated above (GSS failure), it took to long. I found that the problem was related to the fact that GSSAPIAuthentication was on by default on ssh server and the server had no reverse dns IP (it has a private address). Disabling GSSAPIAuthentication fixed the issue for me.
I obtain the same error (GSS failure) also connecting to other server that have correct DNS config and GSSAPIAuthentication enabled but in these servers I don't realize about the error because of there is no delay in the connection (thanks to right DNS direct and reverse loookup).
I say again that I don't know GSSAPI so if the error could be related to the fact that I have no kerberos system we could mark the bug as "invalid" or similar.
Excuse me Chuck but the problem is clear.
When you do
ssh -v SERVER.DOMAIN
you obtain an output similar to the following: .ssh/identity type -1 .ssh/id_ rsa type -1 .ssh/id_ dsa type -1 OpenSSH_ 4.7p1 Debian-8ubuntu1.2 KEX_DH_ GEX_REQUEST( 1024<1024< 8192) sent KEX_DH_ GEX_GROUP KEX_DH_ GEX_INIT sent KEX_DH_ GEX_REPLY .ssh/known_ hosts:87 SERVICE_ REQUEST sent SERVICE_ ACCEPT received gssapi- with-mic, password
"
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to wall [141.250.199.62] port 22.
debug1: Connection established.
debug1: identity file /home/marcop/
debug1: identity file /home/marcop/
debug1: identity file /home/marcop/
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-
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_
debug1: expecting SSH2_MSG_
debug1: SSH2_MSG_
debug1: expecting SSH2_MSG_
debug1: Host 'wall' is known and matches the RSA host key.
debug1: Found key in /home/marcop/
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_
debug1: SSH2_MSG_
debug1: Authentications that can continue: publickey,
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
debug1: Next authentication method: publickey .ssh/identity .ssh/id_ rsa .ssh/id_ dsa
debug1: Trying private key: /home/marcop/
debug1: Trying private key: /home/marcop/
debug1: Trying private key: /home/marcop/
debug1: Next authentication method: password
"
There is no crash and no way to report it via apport.
I don't know what "Unspecified GSS failure" means. I have no kerberos system installed in my network (maybe could be this?).
However my problem was related to the fact that connecting to a server via ssh, apart from displaying the error indicated above (GSS failure), it took to long. I found that the problem was related to the fact that GSSAPIAuthentic ation was on by default on ssh server and the server had no reverse dns IP (it has a private address). Disabling GSSAPIAuthentic ation fixed the issue for me.
I obtain the same error (GSS failure) also connecting to other server that have correct DNS config and GSSAPIAuthentic ation enabled but in these servers I don't realize about the error because of there is no delay in the connection (thanks to right DNS direct and reverse loookup).
I say again that I don't know GSSAPI so if the error could be related to the fact that I have no kerberos system we could mark the bug as "invalid" or similar.