Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support path setting for LOAD DATA INFILE #202

Open
HOSTED-POWER opened this issue Oct 26, 2018 · 1 comment
Open

Support path setting for LOAD DATA INFILE #202

HOSTED-POWER opened this issue Oct 26, 2018 · 1 comment

Comments

@HOSTED-POWER
Copy link

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

@HOSTED-POWER
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants