[debian-mysql] mysql-5.7: secure_file_priv

[Lars Tangvald]

Hi Björn, 


Nice! I've also been working on a 5.7 branch (possibly from the other end, as I started with the way we build our own packages). I'm still on vacation, but I'll look into the secure_file_priv option and get back to you about it. 


-- 
Lars 
----- Original Message ----- 
From: bjoern at boschman.de 
To: pkg-mysql-maint at lists.alioth.debian.org 
Sent: Tuesday, December 29, 2015 6:57:50 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna 
Subject: [debian-mysql] mysql-5.7: secure_file_priv 


Hi folks, 

I've started working on a mysql-5.7 branch [0]. 

While doing so I had to phase the following difference between 5.6<->5.7 

secure_file_priv [1] 

mysql-5.6 default for this setting was 'empty' which simply disables this feature. 
mysql-5.7 builds with (what we currently do) '/var/lib/mysql-files' which is based on the used INSTALL_LAYOUT=RPM [2] 

my question is now: how shall I handle this? 
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. 

I'm thinking of switching INSTALL_LAYOUT=STANDALONE as this seems to be the only usage of this cmake flag. 


@Oracle employees: can you confirm that this has no other impact? 

[0] http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.7.git/ 
[1] https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_secure_file_priv 
[2] https://dev.mysql.com/doc/refman/5.7/en/source-configuration-options.html#option_cmake_install_layout 
-- 
Mit freundlich Grüßen / Kind regards 

Björn Boschman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20151229/b5e7c385/attachment.html>