[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-security] Re: /bin/login problem

Wietse Venema:
> [ having getty select the tty for readability without actually
> reading the login name from stdin]
> Yes, this means that you lose all those cutesy features of my agetty
> program [...]

Rogier Wolff:
> One of the classical "getty" features that you loose this way is 
> the autobauding that classical getty's perform. (i.e. read a
> character, and change the baudrate whenever it's "bad")

True, however with today's speed-buffering modems this behavior
can be undesirable. At least I haven't needed speed switching in
my agetty program since I hooked up a ZyXEL modem in 1991 or so.

One also loses detection of parity, erase and kill characters.
Loss of parity detection can be a problem with 7-bit terminal
settings. So it seems best to preserve getty functionality.

Does LINUX have the moral equivalent of the TIOCSTI ioctl() call
(simulate tty input)? If so, that could be used by (a)getty to
stuff the login name back after reading it, so that /bin/login can
pick it up from STDIN.

[mod: Yes. -- REW]


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]