Rafal Maszkowski <[EMAIL PROTECTED]> writes:
> After long break I tried lsh again trying to look at it from a fresh user (or
> ssh user) perspective. My remarks:
Thanks.
> Lsh says:
>
> Failed to open '/root/.lsh/identity' (errno = 2): No such file or directory.
> Failed to open '/root/.lsh/known_hosts' (errno = 2): No such file or directory.
>
> It could create something itself.
These messages are harmless, it tries to opens the files, but can do
without them. Probably, it shouldn't tell you about it. It's not much
point in creating the files, as lsh doesn't know what to put there.
> lsh: Server's hostkey is not trusted. Disconnecting.
>
> There is no question if we'd like to connect anyway.
>
> It is not asking if the user would like to add new keys to known_hosts
The default mode is paranoid.
Use --sloppy-host-authentication, and perhaps even
--capture-to=~/.lsh/known_hosts, to get less paranoid behaviour.
I believe that sloppy operation is the exception (even if it is
usually what you want the first few times), so I don't want to make it
the default behaviour.
> There is no way suspend the session with some ^Z (~^Z in ssh).
There's no escape character. That's a missing feature.
You should be able to suspend lsh by sending it the right signal,
though. If you run it in pty mode (i.e. without the -nt option), you
can't do that from the terminal; you have to type the right kill
command on a different terminal.
> I got such errors when usng lsh -z:
> do_zlib: Estimated size exceeded: input = 9, estimate = 200, output = 216
These messages are harmless; they should probably be disabled except
in debug mode.
> And finally:
> rzm@pingwin:~,1> exit
> logout
> Sending EOF on channel 0 [pressed enter]
> read_data: Receiving data on closed channel. Ignoring.
>[hanging]
The hang is somewhat strange. What does the other side say? Can you
run it in debug mode?
The read_data message is harmless, but it indicates that lsh doesn't
close it's stdin when it should.
/Niels
