On 01/18/2017 10:09 AM, Tom Rivers wrote: > On 1/18/2017 12:24 PM, Rick Stevens wrote: >> That's normal. The system (or shell) is echoing the input because the >> program you expect to consume the input isn't running or hasn't >> finished initializing yet. What do you expect the system to do? Not >> echo anything unless explicitly told to? > > Perhaps I'm missing something here, but the answer to this dilemma seems > to be as simple as don't ask for a password until you are ready to > ensure it is handled properly. More to the point, if the place on the > display where a password is supposed to be entered is not shown, then a > user won't be tempted to enter it. The fact a password field is > displayed should mean that the system is ready to deal with it > appropriately. Otherwise we can potentially get a "cart before the > horse" situation like this one. That's not what's happening here. The user is starting a program, then immediately typing in the expected password before the program starts, essentially making use of the type-ahead capability of the shell. The program hasn't, well, "registered" its stdin yet so the data is echoed to the screen as there's no where else for it to go. There is no way for the shell to know it shouldn't echo the data. The only way I can see for this to not happen is to disable type-ahead in the shell. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - -"Jimmie crack corn and I don't care." What kind of a lousy attitude - - is THAT to have, huh? -- Dennis Miller - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
