Hi, William! You, likely, mean mariadb-server-10.2 or mariadb-server-10.3. This was a transitional period, in a sense. Debian packages have switched to the unix_socket authentication and MariaDB packages haven't. Since 10.4 both Debian and MariaDB packages use unix_socket authentication and a passwordless root account. Before 10.2 (?) both Debian and MariaDB packages had debian-sys-maint user and three root accounts with a password. Regards, Sergei VP of MariaDB Server Engineering and security@mariadb.org On Jun 26, William Edwards wrote:
Hello,
I recently discovered a bug in my MariaDB deployment process. I have two Ansible tasks that respectively add the downloads.mariadb.org Debian repo, and install mariadb-server-10.*. I forgot to add 'update_cache: yes' to the repo add task, so incidentally mariadb-server-10.* was actually installed from the Debian repo. I have seen the following differences between the mariadb-server-10.* packages:
- Packages from Debian repo only come with the 'root@localhost' user. Packages from MariaDB repo come with the users 'root@localhost', 'root@::1' and 'root@127.0.0.1'. - Packages from Debian repo don't come with 'debian-sys-maint@localhost' user. Instead, the 'root' user is used in /etc/mysql/debian.cnf - Packages from Debian repo use DebianAlternatives for my.cnf. Packages from MariaDB repo also come with a more advanced my.cnf, e.g. 'bind-address = 127.0.0.1' is set - not being able to remotely connect is how I discovered this bug on my side. - Packages from MariaDB repo come with package configuration (specifically: setting root password).
Q: I'm wondering if anyone has a more complete list of differences between these packages (the above is just what I've observed from fixing issues due to this bug).
I don't know if the Debian maintainers for this package branch off a package by MariaDB, so I posted this here, but please let me know if I would be better off posting this on a Debian mailing list.