OpenSSH 2.9p1 on Solaris 7 error, 2 bugs

Jason Keltz jas at cs.yorku.ca
Thu May 17 01:55:30 EST 2001


Hi.

I am running OpenSSH 2.9p1 on Solaris 7, and I believe that I have
identified a bug that has been annoying several of our faculty.

Our SSH server has 4 addresses:

Name:    tiger.cs.yorku.ca
Addresses:  130.63.88.26, 130.63.90.26, 130.63.92.26, 130.63.86.26

If I do:

% ssh -X tiger

I am able to login to tiger, and run X applications.

However, the IP addresses cycle for tiger on name lookups like on any
multi-IP host, so after a short period of time, X applications cannot
be started any more.

For example, after a successful connection via ssh -X tiger:

tiger 316 % xterm -display 130.63.92.26:12.0
X connection to 130.63.92.26:12.0 broken (explicit kill or server shutdown).
tiger 317 % xterm -display 130.63.86.26:12.0
X connection to 130.63.86.26:12.0 broken (explicit kill or server shutdown).
tiger 318 % xterm -display 130.63.88.26:12.0
X connection to 130.63.88.26:12.0 broken (explicit kill or server shutdown).
tiger 319 % xterm -display 130.63.90.26:12.0
<application starts>

If I set the DISPLAY variable to 130.63.90.26:12.0, everything will work
for this particular connection, but you never know what the 'magic'
address is going to be unless you test them all.

This doesn't work with v1 or v2 ssh protocols.

I have a "tiger-bk" address which is just 130.63.92.26, but ssh is 'smart'
and does a reverse lookup, setting DISPLAY to tiger, so this doesn't solve
the problem.

Any help that you can provide would be greatly appreciated.

Thanks!

Jason Keltz
jas at cs.yorku.ca




More information about the openssh-unix-dev mailing list