[925] in NetBSD-Development
Unencrypted rlogin problem solved
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jul 31 02:01:46 1995
Date: Mon, 31 Jul 1995 02:00:29 -0400
From: Greg Hudson <ghudson@MIT.EDU>
To: netbsd-dev@MIT.EDU
The unencrypted rlogin problem was that klogind and login.krb weren't
unsetting and resetting IEXTEN in the termios flags while transmitting
the authenticator, so ^O (at least) was elided. I've fixed this and
installed the fix on the system packs (all in AFS, fortunately) and on
jaws.
POSIX 7.1.2.5 states:
If IEXTEN is set, implementation-defined functions shall be
recognized from the input data. It is implementation defined
how IEXTEN being set interacts with ICANON, ISIG, IXON, or
IXOFF. If IEXTEN is not set, then implementation-defined
functions shall not be recognized, and the corresponding input
characters shall be processed as described for ICANON, ISIG,
IXON, and IXOFF.
So it's NetBSD's decision whether or not to interpret ^O when ICANON
and ISIG are disabled, and the rlogind code was of course patently
wrong. I think NetBSD shouldn't interpret ^O when ISIG isn't set,
though.
