Hi, I discovered a strange problem with the latest version (2.9.9p2) and previous versions of OpenSSH when using portforwarding und Solaris 8 x86. It seems like the getaddrinfo() function on Solaris 8 x86 is somehow broken, instead of binding a port to 127.0.0.1, OpenSSH tried to bind it to 1.0.0.127 (1.0.0.127 was the ai->ai_addr returned by getaddrinfo() in channel.c). I could not reproduce this on Solaris 8 Sparc and I assume that Sun developers mixed endianess on the x86 platform. I could fix the problem by marking the getaddrinfo() function as broken on Solaris 8 x86 (#define BROKEN_GETADDRINFO 1). Maybe someone of you could recheck this problem and try to find a better fix for it. Regards, Konrad -- Konrad Rieck <kr at roqe.org> Roqefellaz - http://www.roqe.org, Public Key http://www.roqe.org/keys/kr.pub -- Fingerprint: 5803 E58E D1BF 9A29 AFCA 51B3 A725 EA18 ABA7 A6A3
openssh-unix-dev at thewrittenword.com
2001-Oct-02 15:35 UTC
Probably broken getaddrinfo() on Solaris x86.
On Tue, Oct 02, 2001 at 01:28:16PM +0200, Konrad Rieck wrote:> I discovered a strange problem with the latest version (2.9.9p2) and previous > versions of OpenSSH when using portforwarding und Solaris 8 x86. > > It seems like the getaddrinfo() function on Solaris 8 x86 is somehow broken, > instead of binding a port to 127.0.0.1, OpenSSH tried to bind it to > 1.0.0.127 (1.0.0.127 was the ai->ai_addr returned by getaddrinfo() in > channel.c). > > I could not reproduce this on Solaris 8 Sparc and I assume that Sun > developers mixed endianess on the x86 platform. > > I could fix the problem by marking the getaddrinfo() function as broken > on Solaris 8 x86 (#define BROKEN_GETADDRINFO 1). > > Maybe someone of you could recheck this problem and try to find a better > fix for it.I just checked sunsolve.sun.com and I think patch id 111328-01 fixes this problem. I don't have a Sol 8/Intel machine to test. -- albert chin (china at thewrittenword.com)