Re: GLUG: ssh problems with 2.4.0/1

[Andrew McGill <andrew@xxxxxxxxxxx>]

On Jan 31 at 15:18, my computer said Chris Fowler said:

> I have recently upgraded my server from 2.2.17 to 2.4.0 and now sshd
> has stopped working. Every time I try to connect with ssh the sshd on
> the server dies . I have just upgraded to 2,4,1 and the same thing
> happens. Does anybody know what the problem is? I remember reading
> that signal 11 can mean bad memory but a kernel compiles with no
> problems and this problem doesn't happen with 2.2.17, I have also
> recompiled openssl and openssh. Any help will be appreciated
> 
> The output is as follows
//snip
Signal 11 is segmentation violation -- and you may have hit on an
exploitable bug if we are all very unlucky.

Did you compile sshd from source?  If so, you can set ulimit -c 9999999 ;
so that when you generate the error sshd will dump core.  Then fire up
gdb, enter "core core" and do a "backtrace".  You could also run ltrace
sshd or strace sshd -- which will spew oodles of output, but could
possibly isolate the problem.

You didn't perhaps compile your kernel without support for ipv4?

&:-)


-- 
LINUX TRAINING
     Course:  Introduction to Linux                           -o)
       Date:  Tuesday 27 February 2001                        /\\
       Cost:  R2120.00 incl. VAT                             _\_v
   Duration:  5 evenings, 7:00 p.m. - 9:00 p.m.
   Includes:  Copy of SuSE Linux 7.0, course notes, refreshments
    Details:  http://www.ledge.co.za/training.phtml
    Contact:  training@xxxxxxxxxxx, or fax 011-803-7928

Leading Edge Business Solutions - www.ledge.co.za - 011-807-0453

     If you don't understand or are scared by any of the above
             ask your parents or an adult to help you.