Bug #35096 Wrong database name in access denied error message for information_schema db.
| Submitted: | 6 Mar 2008 8:39 | Modified: | 21 Apr 2008 18:04 |
|---|---|---|---|
| Reporter: | Kristofer Pettersson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Security: Privileges | Severity: | S3 (Non-critical) |
| Version: | 6.0 | OS: | Any |
| Assigned to: | Kristofer Pettersson | CPU Architecture: | Any |
[6 Mar 2008 8:39]
Kristofer Pettersson
[6 Mar 2008 18:01]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/43543 ChangeSet@1.2591, 2008-03-06 19:07:43+01:00, thek@adventure.(none) +4 -0 Bug#35096 Wrong database name in access denied error message for information_schema db. When table access was denied for information_schema, the current db was shown in the error message instead of the target database.
[7 Mar 2008 10:21]
Sergei Glukhov
ok to push
[20 Apr 2008 13:00]
Bugs System
Pushed into 6.0.6-alpha
[21 Apr 2008 18:04]
Paul DuBois
Noted in 6.0.6 changelog. Access-denied messages for INFORMATION_SCHEMA incorrectly showed the name of the default database instead.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.