haynes@saturn.ucsc.edu ( Computer Center) (12/29/87)
We run a port selector, which types a fair amount of message-of-the-day to the user's terminal; but this might happen even without a port selector. If the terminal is in a slow scrolling mode it can't always keep up with incoming characters at 2400 baud, so it will try to restrain input with ctrl-S, and follow with ctrl-Q when it catches up. We found this happening with the initial getty message and login: prompt. The result is that the user's login name is prefixed by ^S^Q and the first attempt to log in always fails. I'm wondering if there is any reason not to modify getty and login to strip out any funny characters in the login name.
hmm@laura.UUCP (Hans-Martin Mosner) (01/02/88)
In article <1505@saturn.ucsc.edu> haynes@ucscc.ucsc.edu (Jim Haynes - Computer Center) writes: > I'm wondering if there is any reason not to modify getty and login >to strip out any funny characters in the login name. I think that modifying getty & login is relatively safe. We have done it here on our uucp machine where the incoming lines are connected to a x.25 PAD. The PAD sends an XON when it gets an incoming call, which has to be ignored by getty. I know, in this case we could just tell our uucp partners to change their L.sys entries for unido, but there are so many of them... Hans-Martin -- Hans-Martin Mosner | Don't tell Borland about Smalltalk - | hmm@unido.{uucp,bitnet} | they might invent Turbo Smalltalk ! | ------------------------------------------------------------------------ Disclaimer: Turbo Smalltalk may already be a trademark of Borland... D
dave@lsuc.uucp (David Sherman) (01/04/88)
haynes@ucscc.ucsc.edu (Jim Haynes) writes: >We run a port selector, which types a fair amount of message-of-the-day to >the user's terminal; but this might happen even without a port selector. > >If the terminal is in a slow scrolling mode it can't always keep up with >incoming characters at 2400 baud, so it will try to restrain input with >ctrl-S, and follow with ctrl-Q when it catches up. We found this happening >with the initial getty message and login: prompt. The result is that the >user's login name is prefixed by ^S^Q and the first attempt to log in always >fails. I'm wondering if there is any reason not to modify getty and login >to strip out any funny characters in the login name. Should be no problem. We did that years ago, along with other, similar changes to accommodate an environment of a thousand new computer-naive law students a year, spread out across the province and using, in some cases, very peculiar equipment which may have been set up for them by someone else. Our getty and login do things such as - mapping all chars to lower-case (instead of the stty LCASE nonsense which goes back to the days of caps-only terminals); - mapping the password to lower-case and trying again if password fails; - stripping out ^S and ^Q - ignoring spaces in the login name etc. David Sherman The Law Society of Upper Canada Toronto -- { uunet!mnetor pyramid!utai decvax!utcsri ihnp4!utzoo } !lsuc!dave Pronounce it ell-ess-you-see, please...
haynes@saturn.ucsc.edu ( Computer Center) (01/05/88)
The answer turns out to be, at least for 4.2 and 4.3 BSD, that this is already provided for. All you have to do is set the "ig" (ignore garbage) flag in /etc/gettytab under "default". Thanks to all who responded.