Keresztfalvi Gabor <[EMAIL PROTECTED]> writes:
> On 11 Apr 2000, Niels M�ller wrote:
> > That's bad. Can you get a C backtrace (either by running lshd inside
> > gdb, or with the --enable-core option so that you get a core dump to
> > analyze)?
> Here it goes:
Thanks. I've also been able to reproduce the problem on my system.
> BTW if I use an ssh2 client from SSH Inc. the problem still occures...
> Seems to be a problem in the server, maybe it gets confused, when the
> executed command terminates and no more data comes from it (but the
> buffers may contain some)?
DEfinitely, something like that is happening. BTW, if the lshd server
crashes for *any* reason [1], that is definitely a bug. It doesn't
really matter if it is lsh, or ssh2, or some exploit script that makes
it fall over.
[1] except by kill -ABRT executed by a local user with the right
privileges ;-)
/Niels
