Bug #48510 Flag for allow/disallow set password without SUPER priv and documentation update
Submitted: 3 Nov 2009 17:10 Modified: 8 Jan 2011 0:20
Reporter: Roger David Nay Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S2 (Serious)
Version:5.0+ OS:Any
Assigned to: Jon Stephens CPU Architecture:Any

[3 Nov 2009 17:10] Roger David Nay
Description:
Customers have 5.0 to 5.1 replication. The different behaviour for set password between versions using read_only GLOBAL variable can cause a problem here.

See related bug http://bugs.mysql.com/bug.php?id=27440

There is no mention of the 5.0 which allows a user to change their password in the 5.0 documentation. There is also no mention of this in the 5.1 documentation either.

How to repeat:
See http://bugs.mysql.com/bug.php?id=27440

Suggested fix:
Either a change to 5.0/5.1 to allow/disallow this with a variable.

A documentation change explaining that 5.0 has the exception of allowing the update in the 5.0 AND 5.1 documentation.
[3 Nov 2009 18:04] Valeriy Kravchuk
Thank you for the feature request.
[23 Nov 2010 16:15] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.
[7 Jan 2011 22:20] Jon Stephens
Re-opening. Seems I misinterpreted some things.
[8 Jan 2011 0:20] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Commit which fixes this properly is here:

http://lists.mysql.com/commits/128209