Linux 4.2p1 crash during reverse name lookup

[Darryl L. Miles]

Peter wrote:

 > Was OpenSSH build on/specifically for the target system?

I was building my own version into a location outside of the platforms standard packaging (RPM/YUM) functions and the platforms packages one is disabled.



 > It doesn't seem to be in OpenSSH, no.

The problem system FedoraCore2 is using glibc 2.3.3, I have repeated the same thing on a CentOS4.2 based system using glibc 2.3.4 and



> > [pid  4657] stat64("/usr/lib/sse2", 0xbfffd4fc) = -1 ENOENT (No such 
> > file or directory)
> > [pid  4657] open("/usr/lib/libnss_dns.so.2", O_RDONLY) = -1 ENOENT (No 
> > such file or directory)
> > [pid  4657] stat64("/usr/lib", 0xbfffd4fc) = -1 ENOENT (No such file or 
> > directory)
> > [pid  4657] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>   

> This crash is inside the glibc resolver, upgrade glibc would be my
> advice.

With glibc 2.3.4 not crash but:

[pid 13660] stat64("/usr/lib/sse2", 0xbfffcb68) = -1 ENOENT (No such file or directory)
[pid 13660] open("/usr/lib/libnss_dns.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 13660] stat64("/usr/lib", 0xbfffcb68) = -1 ENOENT (No such file or directory)
[pid 13660] geteuid32()                 = 74
[pid 13660] write(3, "\314\24\323b\272\1r]r\363\300\5\337\22\366\212\340\35*\260\25\361\214]\r\200@\37p6\336(!=\0176\250\261\37\0\367\303\207uv&2\n\0\215\337\311-\214-v\312\306\321\233\360\216\374\367\306\243vX\224[\260n4b\22C{\v \r\32\251\340o", 84) = 84
[pid 13660] select(4, [3], NULL, NULL, NULL


Thanks for the pointers.


-- 
Darryl L. Miles