On 30 Dec 1999, Niels M�ller wrote:
> "Eric J. Schwertfeger" <[EMAIL PROTECTED]> writes:
>
> It seems the client requested a pty, and crashed when it couldn't get
> one. In this case, it is supposed to just go on, but not bother trying
> to do things like setting the tty into raw mode.
When I edited config.h to fix PTY_BSD_SCHEME_FIRST_CHARS and
PTY_BSD_SCHEME_SECOND_CHARS by hand, it worked. So the previously
mentioned problems are all that have to be overcome before FreeBSD has an
unencumbered encrypted login method :-) (I know, I've seen the warnings,
but lsh can't be worse than telnet throwing unencrypted passwords around,
as long as there's no buffer overflows or other serious problems of that
nature).
I'll look into POLLIN vs POLLRDNORM.
The PTY_BSD_SCHEME_FIRST_CHARS can be fixed either by figuring out what
the problem is in the configure script, or by making openpty work, and
tweaking things so that it uses openpty before the traditional method that
uses PTY_BSD_SCHEME_(FIRST|SECOND)_CHARS.
