On 30 Dec 1999, Niels M�ller wrote:
> "Eric J. Schwertfeger" <[EMAIL PROTECTED]> writes:
> > Here it sits, not listening to port 4711 according to netstat. In fact,
> > according to netstat, there aren't any new ports in listen mode since
> > before I started the program.
> >
> > Would someone mind sending me the output of what this is supposed to look
> > like?
> It seems lshd doesn't realize that there is data available from the
> file NEW_KEY, and poll() is hanging. What does truss (or strace,
> whatever the syscall tracing program is called) say about the lshd
> process? Do you have poll(), or is lshd using the poll-by-select
> wrapper?
Sorry if I'm giving a lot of irrelevant details, I'm just excited to be
making as much progress as I am :-) I'll have this working yet.
It's using poll(). I just tracked down the problem, but I'm not sure what
to do with it. Probably going to see what POSIX has to say about poll().
Basically, if I replace POLLIN with POLLRDNORM, it reads NEW_KEY. In
fact, it almost works, except for
lsh: Server's hostkey is not trusted. Disconnecting.
Probably because I ran both lsh and lshd as a regular user, and haven't
set up the trust databases yet.
adding --sloppy-host-authentication fixes that, but now it just keeps
prompting for the password, and the server logs
Raising exception Wrong password
So, I ran lshd as root (I don't think programs can verify passwords under
FreeBSD without root permissions), and this time lsh prints
Unhandled exception of type 0x8002: Channel request failed
At this point, I had to bring this back to the list. I think this is
where it was failing when I tried earlier versions of lsh.
I captured the output with the script command, so if anyone wants more
details, the files are
http://geekzilla.geekazoid.com/lsh.client.txt
http://geekzilla.geekazoid.com/lsh.server.txt
