Cybersecurity

I suppose the problem to be on the server side of the communication: check "/etc/sshd_config" or whatever else you use as a configuration file for "sshd". Restart "sshd" after any changes you make there to read in the new configuration.

I hope this helps.

bakunin

Thanks bakunin.

Unfortunately, I don't have the permission to restart sshd.

The thing is that I did not change anything in the sshd config, but simply generated the keys. You think this may be related?

Aaron

Then get someone who can to analyze the problem.

No, not at all. But ssh-communication requires two things to work in accordance: the client side (ssh-client, authentication data) and the server side (the sshd daemon and its configuration).

I don't claim to know what went wrong in your case, but the debug output you provided makes me suppose the problem is with the server side. To verify this one will have to examine the server configuration and eventually reconfigure/restart it, as i have told you.

Alternatively you can try to set up communication from a third host to the problematic one: if i got you correctly "HostA->HostB" works, but "HostB->HostA" doesn't. Set up "HostC->HostA" and see if this works. If it does it is probably not the sshd in host A as such, but maybe just the configuration: there are different versions of open-ssl (the library which does the underlying encryption) and maybe you hit upon such a version incompatibility.

Fact is: i don't know and as long as you can't present more and better data probably nobody can. So we are left to suggestions and more or less educated guesses about possible reasons.

I hope this helps.

bakunin