<div dir="ltr">Hi folks,<br><br>I've started working on a mysql-5.7 branch [0].<br><br>While doing so I had to phase the following difference between 5.6<->5.7<br><br>secure_file_priv [1]<br><br>mysql-5.6 default for this setting was 'empty' Â which simply disables this feature.<br>mysql-5.7 builds with (what we currently do) '/var/lib/mysql-files' which is based on the used INSTALL_LAYOUT=RPM [2]<br><br>my question is now: how shall I handle this?<br>I would not like to add Â secure_file_priv= within mysqld.cnf as this would deactivate this feature for customers who want to use this on purpose.<br><br>I'm thinking of switching INSTALL_LAYOUT=STANDALONE as this seems to be the only usage of this cmake flag.<div><br></div><div>@Oracle employees: can you confirm that this has no other impact?<br><br>[0] <a href="http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.7.git/">http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.7.git/</a><br>[1] <a href="https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_secure_file_priv">https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_secure_file_priv</a><br>[2] <a href="https://dev.mysql.com/doc/refman/5.7/en/source-configuration-options.html#option_cmake_install_layout">https://dev.mysql.com/doc/refman/5.7/en/source-configuration-options.html#option_cmake_install_layout</a><br>--<br>Mit freundlich Grüßen / Kind regards<br><br>Björn Boschman</div></div>