| Bug #86838 | SET PASSWORD on a 5.6 master will create a different hash on a 5.7.x slave | ||
|---|---|---|---|
| Submitted: | 27 Jun 2017 15:48 | Modified: | 27 Jun 2017 16:59 |
| Reporter: | Riccardo Pizzi | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.7.18 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[27 Jun 2017 15:49]
Riccardo Pizzi
Fixed synopsis
[27 Jun 2017 16:59]
MySQL Verification Team
Thank you for the bug report. Duplicate of https://bugs.mysql.com/bug.php?id=82979.
Description: When issuing the command: SET PASSWORD FOR 'user'@'%' = PASSWORD('somepass') on a 5.6 master, the information seem to be wrongly stored on the 5.7 slave and the user cannot access anymore. We verified that the stored hash for the user is different on the 5.6.24 master and the 5.7.18 slave. How to repeat: Change the password on the 5.6 master with SET PASSWORD FOR 'user'@'%' = PASSWORD('somepass') Check hash on the 5.6 master (column password in mysql schema) and on the 5.7 slave (column authentication_string in mysql schema), they will be different. Only fix is to run alter user 'user'@'%' IDENTIFIED BY 'somepass' on the slave using another user....