You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mysql> show global variables like 'secure_file_priv';
+------------------+-----------------------+
| Variable_name | Value |
+------------------+-----------------------+
| secure_file_priv | /var/lib/mysql-files/ |
+------------------+-----------------------+
1 row in set (0.00 sec)
Could you use this path or better allow the path for this operation to be set instead of /tmp ?
It would allow a much more secure setting on mysql ...
We also noticed that pimgento seems to insist on /tmp folder, is this correct? PrivateTmp, which is the default since 2014 on CentOS 7 and many other distributions, will not allow pimgento to find the path.
Any solutions besides making the setup even more insecure?
mysql> show global variables like 'secure_file_priv';
+------------------+-----------------------+
| Variable_name | Value |
+------------------+-----------------------+
| secure_file_priv | /var/lib/mysql-files/ |
+------------------+-----------------------+
1 row in set (0.00 sec)
Could you use this path or better allow the path for this operation to be set instead of /tmp ?
It would allow a much more secure setting on mysql ...
Now we need to allow LOAD DATA INFILE for the whole server which is insecure, read more here: https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_secure_file_priv
The text was updated successfully, but these errors were encountered: