Bug #59044 secure_file_priv does not respect Windows file naming standard

• Submitted: 19 Dec 2010 19:18
• Modified: 4 Aug 2015 4:25
• Reporter: Roel Van de Paar
• Status: Closed
• Category: MySQL Server: General
• Severity: S3 (Non-critical)
• Version: 5.1.39, 5.1.55
• OS: Windows
• Assigned to: Assigned Account
• CPU Architecture: Any

[19 Dec 2010 19:18] Roel Van de Paar

Description:
VERSION(): 5.1.55-debug

| secure_file_priv | C:\test\ |

mysql> load data infile 'c:/test/test.txt' into table t1;
ERROR 1290 (HY000): The MySQL server is running with the --secure-file-priv option so it cannot execute this statement

mysql> load data infile 'C:/test/test.txt' into table t1;   /* note the uppercase C */
Query OK, 1 row affected (0.02 sec)
Records: 1  Deleted: 0  Skipped: 0  Warnings: 0

How to repeat:
Use upper/lower cases combination

Suggested fix:
c: should work also, as it is valid on Windows

[3 Aug 2015 11:14] MySQL Verification Team

This seems to be fixed..

mysql> select 1 into outfile 'E:/sec/b/ggg.txt';
Query OK, 1 row affected (0.00 sec)

mysql> select @@secure_file_priv,version();
+--------------------+---------------------------------------+
| @@secure_file_priv | version()                             |
+--------------------+---------------------------------------+
| E:\sec\            | 5.6.26-enterprise-commercial-advanced |
+--------------------+---------------------------------------+
1 row in set (0.01 sec)

mysql> select 1 into outfile 'E:/sec/b/eee.txt';
Query OK, 1 row affected (0.00 sec)

mysql> select 1 into outfile 'e:/sec/b/fff.txt';
Query OK, 1 row affected (0.00 sec)

[3 Aug 2015 11:20] MySQL Verification Team

i suspect the fix came with this change:
https://github.com/mysql/mysql-server/commit/4c5dfc00f7a2ea3cf9475455e2749a96bfc38344

[4 Aug 2015 4:25] Roel Van de Paar

Cool. Closing. Have not tested on Windows (don't use it anymore these days), but if Shane tested it, that's good enough for me :)