You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading mariadb from 10.3.21 to 10.4.11, all Test-mysqld tests fail like this:
$ perl -Ilib t/01-raii.t
DBI connect('dbname=mysql;mysql_socket=/tmp/cXEW5xhQn2/tmp/mysql.sock;user=root','',...) failed: Access denied for user 'root'@'localhost' at lib/Test/mysqld.pm line 143.
Access denied for user 'root'@'localhost' at lib/Test/mysqld.pm line 143.
As a result mariadb uses unix socket for a local connection and enforces that the user specified with --user option is equaled to the user who runs the SQL client.
The text was updated successfully, but these errors were encountered:
ppisar
added a commit
to ppisar/p5-test-mysqld
that referenced
this issue
Apr 1, 2020
MariaDB 10.4.3 changed a default authentication mechanism for UNIX
socket connections. As a result tests stated to fail on failed
authentication.
This patch adjusts dsn() computation and a test to omit the erroneous
user=root parameter.
The same MariaDB also started to enforce setting root password. Since
there is no password management in Test::mysqld, skipped fixing this
part of the code. I only left a comment there.
kazuho#32
I should notice that a current mariadb C client library has a broken UNIX socket authentication and a fix [https://jira.mariadb.org/browse/CONC-441?focusedCommentId=146491&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-146491] will be released in mariadb 10.4.13.
After upgrading mariadb from 10.3.21 to 10.4.11, all Test-mysqld tests fail like this:
It seems to be triggered by a change in the default authentication settings https://mariadb.com/kb/en/authentication-plugin-unix-socket/ brought with 10.4.3. Probably with this commit MariaDB/server@7f6d88944c.
As a result mariadb uses unix socket for a local connection and enforces that the user specified with --user option is equaled to the user who runs the SQL client.
The text was updated successfully, but these errors were encountered: