Hi Otto, On 02-10-2020 15:44, Otto Kekäläinen wrote: > The /etc/mysql/debian.cnf file is only root-readable, and intended for > root users to be able to access the database console e.g. when the > maintainer scripts run and start/stop the server.
That's exactly why dbconfig-common reads it. > The new way of using > socket authentication is a superior way from both security and > management point of view. The file has been obsolete for a couple of > years and now I emptied the contents of it. Ack, but you share this file with MySQL. > According to codesearch.debian.net there are quite a few places that > run `mysql --defaults-file=/etc/mysql/debian.cnf` and they will fail > if the file is missing, so it is now there, but empty. In the current implementation, dbconfig-common will fail both ways, empty or absent. > I did not find any code that would change the username and for recent > years the setting has said "user = root", and before that it was > "user = debian-sys-maint" This is (or used to be) the MySQL default. Is MySQL now also using the socket authentication and root? > One option could potentially be that if dbconfig-common does not find > the username, it could default to just "root". I guess that could work, if it works for MySQL as well. Or does MySQL still always create the filled /etc/mysql/debian.cnf file? > I will wait for a couple of days to see if anybody else sends feedback > about /etc/mysql/debian.cnf and then decide what to do. Same for me. Paul
signature.asc
Description: OpenPGP digital signature
