Hi! I've downloaded yesterday the version openssh-4.3p2. Compiled and installed without problems. No optimization options were used, no PAM. sshd starts also without any problem. But when I try to connect to it, the connection is immidiately closed and I get in the dmesg the following sshd[5246]: segfault at 00002aaaaabbfe40 rip 00002aaaaaab0bf3 rsp 00007fffffef54d0 error 7 Here is the output from ldd libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x00002aaaaabc1000) libutil.so.1 => /lib/libutil.so.1 (0x00002aaaaae01000) libz.so.1 => /lib/libz.so.1 (0x00002aaaaaf05000) libnsl.so.1 => /lib/libnsl.so.1 (0x00002aaaab019000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00002aaaab130000) libresolv.so.2 => /lib/libresolv.so.2 (0x00002aaaab265000) libc.so.6 => /lib/libc.so.6 (0x00002aaaab379000) libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab597000) /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) I'm not subscribed to the list, so please send questions directly to me. Voropaev Andrei
On Sat, Apr 08, 2006 at 10:39:59AM +0200, Andrei A. Voropaev wrote: [...]> But when I try to connect to it, the connection is immidiately closed > and I get in the dmesg the following > > sshd[5246]: segfault at 00002aaaaabbfe40 rip 00002aaaaaab0bf3 rsp 00007fffffef54d0 error 7Just wanted to add, that I tried previous version (4.2p1) with exactly the same problem. Finally I've stopped on 3.9p1, which works. Voropaev Andrei
Andrei A. Voropaev wrote:> I've downloaded yesterday the version openssh-4.3p2. Compiled and > installed without problems. No optimization options were used, no PAM. > > sshd starts also without any problem. > > But when I try to connect to it, the connection is immidiately closed > and I get in the dmesg the following > > sshd[5246]: segfault at 00002aaaaabbfe40 rip 00002aaaaaab0bf3 rsp 00007fffffef54d0 error 7What version of OpenSSL and zlib did you compile with? Could you please run ssh and sshd in debug mode and see where the crash occurs? (eg run "/path/to/sshd -ddd -p 2022" then connect to port 2022 with "ssh -vvv -p 2022 yourserver"). Also, if sshd generates a core dump, can you feed it to gdb and get a backtrace ("gdb /path/to/sshd core" the "bt"). -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
On Sat, 8 Apr 2006, Andrei A. Voropaev wrote:> Hi! > > I've downloaded yesterday the version openssh-4.3p2. Compiled and > installed without problems. No optimization options were used, no PAM. > > sshd starts also without any problem. > > But when I try to connect to it, the connection is immidiately closed > and I get in the dmesg the following > > sshd[5246]: segfault at 00002aaaaabbfe40 rip 00002aaaaaab0bf3 rsp 00007fffffef54d0 error 7 > > > Here is the output from ldd > > libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x00002aaaaabc1000) > libutil.so.1 => /lib/libutil.so.1 (0x00002aaaaae01000) > libz.so.1 => /lib/libz.so.1 (0x00002aaaaaf05000) > libnsl.so.1 => /lib/libnsl.so.1 (0x00002aaaab019000) > libcrypt.so.1 => /lib/libcrypt.so.1 (0x00002aaaab130000) > libresolv.so.2 => /lib/libresolv.so.2 (0x00002aaaab265000) > libc.so.6 => /lib/libc.so.6 (0x00002aaaab379000) > libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab597000) > /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) > >From ldd output and kernel error line you provided I suspect a bug in yourglibc, namely in dynamic loader /lib64/ld-linux-x86-64.so.2. OpenSSH 3.9p1 is fine with it, while later releases somehow provoke that bug. -- Sincerely Your, Dan.