Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: dropped connection with openssh4.2

Subject: Re: dropped connection with openssh4.2
Date: Sun, 01 Jan 2006 16:01:35 +1100
Waitman Gobble wrote:
Rebuilding didn't help anything. I cannot connect to openssh4.2p1 but
openssh3.9p1 works fine. Here are the results of the connections, one
for each version. The 4.2p1 abruptly drops the connection at "we sent a
keyboard-interactive packet, wait for reply". Nothing in the log files.

here's a hint: keyboard-interactive. maybe i have always misunderstood
this, i thought it was enabling entry of a password. But from the log
below it doesn't look that way to me. I'll see what tinkering with that
does.

This looks like a bug in glibc that showed up a while back: any name service lookup from a chroot would segfault. There's a thread in the openssh-unix-dev archives about this (search for "gethostbyname" and "chroot").


You can either update your glibc (assuming the patch has been backported to your distro) or work around it: from memory, creating a "/dev" dir inside the chroot (/var/empty by default) prevent the crash.

--
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.

<Prev in Thread] Current Thread [Next in Thread>