Thayne Harbaugh <[EMAIL PROTECTED]> writes:
> 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.
Thanks. Relevant inforamtion could include C backtrace, and the type
of userauthentication (password or public key) that is used. There are
substantial changes in the "user" class since 0.9.
> 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.
I should put that on the TODO-list. What is needed is handling (on lsh
side) and signalling (on the lshd side) of SIGWINCH, as well as
implementation of the corresponding CHANNEL_REQUEST message.
/Niels
