Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a desktop machine C, and two servers: A & B.

I can use my id_rsa.pub to connect to both servers A & B without typing in a password. From A I can connect to B without typing in a password. But from B to A, I am getting some failures. Nothing in the client side verbose output is helpful. I do not have access to the host side auth logs. I have copied the exact same id_rsa* to all machines in question. Permission on all relevant directories are the same (700, 600, og-w, etc.)

Is there any setting which might cause this? (server B is Ubuntu 12.04 and server A is 11.04)

[EDIT]

serverA $ ls -al ~/.ssh/
total 32
drwx------  2 jenkins jenkins 4096 2013-08-30 17:33 .
drwxr-xr-x 12 jenkins jenkins 4096 2013-09-02 10:31 ..
-rw-------  1 jenkins jenkins  231 2013-07-20 14:56 authorized_keys2
-rw-------  1 jenkins jenkins  891 2013-07-25 11:44 id_rsa
-rw-------  1 jenkins jenkins  231 2013-07-20 14:56 id_rsa.pub
-rw-r--r--  1 jenkins jenkins 3980 2013-08-30 17:37 known_hosts

serverB $ ls -al ~/.ssh/
total 28
drwx------  2 jenkins jenkins 4096 Sep  2 10:04 .
drwxr-xr-x 15 jenkins jenkins 4096 Sep  2 10:36 ..
-rw-------  1 jenkins jenkins  231 Jul 20 14:56 authorized_keys2
-rw-rw-r--  1 jenkins jenkins   17 Sep  2 10:04 config
-rw-------  1 jenkins jenkins  891 Jul 25 11:44 id_rsa
-rw-------  1 jenkins jenkins  231 Jul 20 14:56 id_rsa.pub
-rw-r--r--  1 jenkins jenkins 3316 Sep  2 11:20 known_hosts

serverB $ cat ~/.ssh/config
ConnectTimeout 4

[EDIT2]

debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/jenkins/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
share|improve this question
    
Could we see carefully-distinguished output of ls -al ~/.ssh on both A and B edited into the question? –  MadHatter Sep 2 '13 at 16:08
    
The routing is pretty spotty from B to A, the connecttimeout helps me reduce waiting times from 60 seconds to 4 when there's going to be a failure. Sometimes ssh -vvv starts putting out logs right away, sometimes it just hangs until there's a connect timeout. Do you think networking troubles could be messing up the key exchange? –  chugadie Sep 2 '13 at 16:30
add comment

1 Answer

The issue was networking related and went away after routing tables were fixed.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.