| Bug #120663 | Contribution: Bug #44929 #92403 #110570: Fix tty password length handling | ||
|---|---|---|---|
| Submitted: | 12 Jun 2:32 | Modified: | 17 Sep 16:51 |
| Reporter: | OCA Admin (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | CPU Architecture: | Any | |
[12 Jun 2:32]
OCA Admin
[12 Jun 2:32]
OCA Admin
Contribution submitted via Github - Bug #44929 #92403 #110570: Fix tty password length handling (*) Contribution by HANCHUN LIU (Github gitliuhc, https://github.com/mysql/mysql-server/pull/664#issuecomment-4685939414): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_3802380035.txt (text/plain), 5.44 KiB.
[25 Jun 1:15]
Miroslav Rajcic
Thank you for the contribution.
[25 Jun 2:48]
MySQL Admin
Posted by developer: Bug status updated to 'Patch pending'
[29 Jun 8:48]
MySQL Admin
Posted by developer: Bug status updated to 'Documenting'
[29 Jun 21:35]
HANCHUN LIU
Thank you very much for the update. I would be very proud if my contribution is accepted by the MySQL community. I look forward to any further updates.
[17 Sep 16:51]
Edward Gilmore
Posted by developer: Added the following note to the MySQL Server 26.10.0 release notes: The mysql client's interactive -p input could truncate or mishandle passwords longer than 79 bytes, including token-style credentials, causing authentication failures. Interactive input now accepts longer credentials without requiring them on the command line. Errors were returned similar to the following: ERROR 9125 (HY000): An error occurred while validating the access token. Please acquire a new token and retry. Using the command-line workaround could also produce: mysql: [Warning] Using a password on the command line interface can be insecure. Our thanks to Hanchun Liu for the contribution.
[20 Oct 23:33]
HANCHUN LIU
Hi Edward Gilmore, Thank you again for confirming that this contribution will be credited in the MySQL Server 26.10.0 release notes. I noticed that MySQL 9.7.4 has already been released (https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-4.html), but this fix does not appear to be included in it. Since 26.10.0 has not been released yet, I wanted to kindly ask: Is this fix planned to be backported to the 9.7.x branch as well, and if so, could it be reflected in a future 9.7.x release note (e.g., 9.7.5 or later)? Or is this fix intended only for the 26.10.0 branch going forward? I just want to make sure I understand which release line(s) this contribution will ultimately land in. Thank you very much for your time and support. Best regards, Hanchun Liu
