"Eric J. Schwertfeger" <[EMAIL PROTECTED]> writes:
> 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 :-)
What values did configure assign to these defines, and what did you
change it to? I'd like to know why the configure test failed.
> I'll look into POLLIN vs POLLRDNORM.
Please do.
> 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.
It would make sense to prefer openpty() over the PTY_BSD_SCHEME stuff.
It's some time since I touched the pty allocation, but the requirements
are a little different from most other applications. Because the
server needs to tell the client whether or not pty allocation
succeeded, the pty must be opened long before the server forks and
changes uid. So if openpty uses the process's current uid to set up
permissions and stuff, it will likely get them wrong.
Sorry I don't remember all the details; perhaps openpty is just right.
/Niels
