Bug #71498 Destination access check to strict for mysqldbcopy
Submitted: 28 Jan 2014 11:59 Modified: 18 Apr 2014 3:55
Reporter: Mikkel Damsgaard Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities Severity:S2 (Serious)
Version:1.4.1 alpha OS:Linux (Ubuntu 12.04 LTS)
Assigned to: Nuno Mariz CPU Architecture:Any
Tags: permissions, super

[28 Jan 2014 11:59] Mikkel Damsgaard 
Description:
In the documentation for the mysqldbcopy utility, it states that SUPER access is needed if copying functions or procedures and binary logging is enabled.

In the source code in mysql/utilities/common/database.py it always checks the destination for SUPER priviledges.

This makes the tool unusable on managed database systems where the user does not have SUPER privilidges, for example on AWS RDS

How to repeat:
Create a user with create database and create table on "*" and then run mysqldbcopy with that user as a destination.

Suggested fix:
Use the skip_procedures and skip_functions flag to determine if a check should be made for SUPER or just CREATE
[4 Mar 2014 23:06] Chuck Bell 
Fixed in release-1.4.2
[18 Apr 2014 3:55] Philip Olson 
Confirmed, the documentation was updated to reflect this.

http://dev.mysql.com/doc/mysql-utilities/1.4/en/mysqldbcopy.html