Re: Chained command prints password in Clear Text and breaks BASH Session until logout

[Jason Sipula]

So, in other words... User Error.

I guess it makes sense why mysql would get grumpy if both mysqldump and
mysql were both attempting to read from stdin, /dev/tty  or whatever at the
same time. I had [incorrectly] assumed that mysqldump would request input
first, then mysql would after mysqldump closed it's hold on stdin. This was
based on an assumption that keyed input could be given to only a single
program at a time and that the "active" program would block others until it
was finished. However it's now clear that both instances attempt to take
control at the same time and end up fighting, leading to undefined behavior.

There's a saying about assumptions that probably applies here...


On Fri, Jul 12, 2013 at 3:30 AM, Andreas Schwab <schwab@linux-m68k.org>wrote:

> Jason Sipula <alupis1@gmail.com> writes:
>
> > This fixed bash. So it does appear MySQL is disabling echo.Strange that
> it
> > does not re-enable it after it's finished running. I'll take this up with
> > the mysql folks.
>
> Most likely the second instance found the terminal already set to -echo
> after the first instance has started to read the password.  Having two
> processes compete for input is never a good thing.
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>