Bug #64201 | replacing table-level privileges causes failure until clients reconnect | ||
---|---|---|---|
Submitted: | 2 Feb 2012 1:44 | Modified: | 16 Feb 2012 15:06 |
Reporter: | Devananda van der Veen | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Security: Privileges | Severity: | S3 (Non-critical) |
Version: | 5.1.60 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | grant, privilege |
[2 Feb 2012 1:44]
Devananda van der Veen
[2 Feb 2012 10:37]
Peter Laursen
I think it is expected that the privileges for a seesion will reamin the same as at the time seesion started. So if there is a bug it is (in my understanding) if SHOW GRANTS tell different. Peter (not a MySQL person)
[2 Feb 2012 16:43]
Devananda van der Veen
Peter, look again. The privileges within the "foo" session clearly changed between the first (successful) and second (failed) inserts. If the session privileges should not change, then that's a bug. If the session privileges should change, then it's also a bug, since the new schema-level privileges didn't take effect. -Deva
[16 Feb 2012 15:06]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Please read at http://dev.mysql.com/doc/refman/5.1/en/privilege-changes.html: A grant table reload affects privileges for each existing client connection as follows: * Table and column privilege changes take effect with the client's next request. * Database privilege changes take effect the next time the client executes a USE db_name statement.