Bug #108499 | MySQL 8 client does not honour "-p" unless a password is included | ||
---|---|---|---|
Submitted: | 15 Sep 2022 19:02 | Modified: | 15 Nov 2022 19:59 |
Reporter: | Joe Creighton | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 8.0.30 | OS: | Linux (Generic) |
Assigned to: | CPU Architecture: | x86 |
[15 Sep 2022 19:02]
Joe Creighton
[15 Sep 2022 19:05]
Joe Creighton
Corrected Category
[14 Nov 2022 12:50]
MySQL Verification Team
Hello Joe Creighton, Thank you for the bug report. I tried to reproduce your issue with MySQL server 8.0.31 through command-line but I am not seeing any issues at my end. Regards, Ashwini Patil
[15 Nov 2022 19:46]
Joe Creighton
I see in the 8.0.31 release notes that this has been fixed: Following a bug fix in MySQL 8.0.29, if the password was provided in an option file, the mysql client did not prompt for a password if the -p option was specified at login. The client now always prompts for a password when the -p option is specified and uses the specified password, even if an alternative was populated from an option file. (Bug #107205, Bug #34134984)
[15 Nov 2022 19:59]
Joe Creighton
Although the previous bug was the reverse scenario, I'll be testing my scenario -- passing user and "-p" in order to connect as a different user and be prompted for credentials -- as soon as I can patch.