Thayne Harbaugh wrote:
>
> funny, on one of my boxes 0.9.1 gives me "lshd: memory corrupted"
> and then it exits. I'm looking for more information right now.
I should not that this is lshd and not lsh that throws the error
and then exits/segfaults.
> It seems that --debug gives as the last thing:
>
> DEBUG: Received SSH_MSG_USERAUTH_REQUEST *****
> handle_connection: Received packet of type 50 (SSH_MSG_USERAUTH_REQUEST)
> Memory corrupted!
> Aborted
>
> lsh-0.2.5 works fine, though. The stranger thing is that
> the very same lsh-0.9.1 works just fine on another box that
> should be identical.
I just now tried lsh-0.9 and it works just fine. Something
obviously broke in the new version.
> Maybe it's a hardware problem, however
> I would think I would see other symptoms of hardware failure
> if that were the case. Hmmmm.
>
> On another note: has anyone noticed that lsh doesn't deal well
> with terminals changing size (such as resizing an xterm)?
> It seems to grab the number of rows and columns of what the
> terminal was at login time and then it always thinks that the
> terminal stays that same size.
>
> "Niels M�ller" wrote:
> >
> > News for the 0.9.1 release
> >
> > Support for remote commands directly on the lsh command line.
> > New options -S and -E. More features in the proxy.
> >
> > This is a work-in-progress release. But
> >
> > $ lsh some.host ls
> >
> > has actually worked, for me, at least once.
> >
> > Happy hacking,
> > /Niels
