On 1/18/2017 1:25 PM, Rick Stevens wrote:
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.

Sorry, I should have been more specific because I agree with what you just said - there's not a whole lot that can be done about that.  However, my previous comments were directed at the situation the OP identified:

On 1/18/2017 9:51 AM, Patrick Dupre wrote:

When you log from the graphics interface (gnome) and provide the
password, if the system is slow (long response time), then the
password can appear in clear !!!

With respect to Gnome, I would suspect that there is a way to ensure that the prompt for password is only displayed when the system is ready to handle it properly.