Re: GLUG: ssh problems with 2.4.0/1

[Chris Fowler <chris.fowler@xxxxxxxxx>]

On Wed, 31 Jan 2001, Andrew McGill wrote:

> 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?
> 
> &:-)
> 
> 
> 
my kernel did have support for ipv4 because otherwise I wouldn't have been 
able to log in to it to run sshd ;)

I tried looking at the core file but it didn;t create one as it seems sshd
cleans up nicely after itself.

Eventually I downloaded 2.3.0p1 which I didn't realise existed until I did a
bit of research and this version seems to work fine so it appears that my
problems are gone

Thanks for the help
Chris


-- 
--------------------------------------------------------------------------
Chris Fowler	Work: +27 (12) 307 8242   Fax: +27 (12) 307 7575
		Cell: +27 (83) 304 0956
		email: chris.fowler@xxxxxxxxx
--------------------------------------------------------------------------