Score:0

Diagnosing SSH authentication failures when you don't have access to the client

hk flag

We have just upgraded our Infoblox appliance and now the log shipment which occurs via scp is failing with auth issues.

Since this is an appliance and we have no access to the a shell on the box we are having trouble figuring out what is wrong. On the infoblox end all we have in the configuration is hostname, port, username and password. (no option for key :( )

I can invoke scp fine from another host with the credentials.

Any suggestions on finding out what the issue is? (short of putting up a hacked sshd ;)

Score:1
cn flag

You don't need a "hacked" sshd. You should be able to run sshd -ddd to put it into debug mode.

For example...

/usr/sbin/sshd -ddd -p 2222

...would listen on 2222 if you can direct client traffic to that port. If not, stop the system sshd and start a debug listener to test the client with.

With any luck, the server-side debug will help you identify the authentication problem.

Russell Fulton avatar
hk flag
I found that you can also set `LogLevel DEBUG3` in sshd_conf
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.