mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 05:22:25 +01:00
2a37d531be
The server variable opt_secure_file_priv wasn't normalized properly and caused the operations LOAD DATA INFILE .. INTO TABLE .. and SELECT load_file(..) to do different interpretations of the --secure-file-priv option. The patch moves code to the server initialization routines so that the path always is normalized once and only once. It was also intended that setting the option to an empty string should be equal to lifting all previously set restrictions. This is also fixed by this patch.
22 lines
295 B
Text
22 lines
295 B
Text
#
|
|
# Bug50373 --secure-file-priv=""
|
|
#
|
|
CREATE TABLE t1 (c1 VARCHAR(50));
|
|
INSERT INTO t1 VALUES ("one"),("two"),("three"),("four"),("five");
|
|
SHOW VARIABLES LIKE 'secure_file_priv';
|
|
Variable_name Value
|
|
secure_file_priv
|
|
c1
|
|
one
|
|
two
|
|
three
|
|
four
|
|
five
|
|
loaded_file
|
|
one
|
|
two
|
|
three
|
|
four
|
|
five
|
|
|
|
DROP TABLE t1;
|