On Sat, 15 Apr 2000, Eric J. Schwertfeger wrote:
> On 12 Apr 2000, Niels M�ller wrote:
>
> > Ok, I think I have fixed this bug. A new bug-fix release (fixing the
> > reported bugs as well as one not reported) is available at the usual
> > places.
>
> Going back a long time (January, I think), I had reported that under
> FreeBSD, if I tried to use lsh to connect to lshd, had already created an
> identity, had not authorized that identity on the end machine, and did not
> specify --no-publickey, it would cause lshd to exit. Just in case anyone
> is keeping track, 0.9.5 fixed that.
ACK! While it works great on FreeBSD 3.4 and 4.0, lshd seems to be broken
on 3.3 :-( Even tried compiling on 3.4 then moving to 3.3.
Broken as in if you connect to lshd, it goes through host and user
authentication as normal, then lsh abruptly terminates. Propper debugging
info tomorrow, but for now, here's the only thing that looks unusual
do_spawn_shell: Child process
do_exec_shell: Setting up environment.
do_exec_shell: Environment:
'TERM'
'K'
''
'\'
Child 60125 killed by signal 11.
Now that's interesting, actual characters won't cut and paste. The second
item is a space, two upside down question marks, and an umlated E. The
third item appears to be a single space.
Hmmm... Last version that I tried testing on 3.3 was 0.9.1, and it worked.
