Gregory B. Cook writes:
: I have a strange problem. I have installed ssh2(v2.1.0) on 3 systems.
: It works on two of them, but not on the third. The three systems are
: an SP2 running AIX-4.3, an SGI O2 running IRIX-6.5, and an IBM laptop
: running RedHat Linux 6.2. There were no compilation errors or install
: errors and ssh2 seems to work fine on the SP2 and SGI. But, when I
: try to make an ssh2 connection (any kind of connection) from the
: Linux system to another system it fails. A typical connection attempt
: with verbose output would be
[LOG SNIPPED]
: It seems that my password is not being authenticated and the connection
: is then dropped.
ssh2 (as of ssh-2.1.0) tries very hard to not give out too much info
on whether there is a given user on the system, and why the
authentication didn't succeed. This is for security reasons.
By checking the server's logs, you should be able to find the cause.
[SNIP}
: machine using ssh1. The only thing slightly unusual about the Linux
: machine is that its networking is set up dynamically via DHCP, so it
: does not have its own hostname.
OK, here's the key. You probably have "RequireReverseMapping" set to
"yes". Because the server can't reverse map the client's name, it
denies connection. Now, because we don't want to give out why the
attempt failed, we produce the exact same results as if the password
authentication failed.
If this is the case, you should either
a) (the easy way)
set "RequireReverseMapping" to "no" in sshd2_config
b) (the more secure way)
add the client's IP-address to "AllowHosts", again in sshd2_config
--
[[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]]
[work:+358 9 85657425][gsm:+358 50 5170 258][http://www.iki.fi/~sjl]
[SSH Communications Security Corp http://www.ssh.com/]
