[MDEV-19290] mariabackup password with characters @#$ fails to connect Created: 2019-04-19 Updated: 2020-09-23 Resolved: 2020-09-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Authentication and Privilege System, mariabackup |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Hendrey Chikane | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
MariaDB 10.2.22 on Ubuntu // MariaDB 10.5.4 on RHEL |
||
| Description |
|
Fail to connect when using complex password: Maria@#$backup202 but works with a simple password: mypassword Also fails to connect with root account which has all privileges, however, mysql -u mariabackup -p does connect. Failed to connect to MySQL server: Access denied for user 'mariabackup'@'localhost' (using password: YES) |
| Comments |
| Comment by Elena Stepanova [ 2019-04-28 ] | |
|
Please specify the version and the error that you are getting while trying to connect as root (the last line in your description is not that, it's connect as mariabackup user). | |
| Comment by Sylvain ARBAUDIE [ 2020-09-18 ] | |
|
i reproduced the bug on MariaDB galera 10.2.22 and on 10.5.4 ??MariaDB [(none)]> create user 'test1'@'localhost' identified by 'P4$$word'; [root@srv-gra2-mdb3 ~]# mysql -utest1 -p [root@srv-gra2-mdb3 ~]# mariabackup --user=test1 --password=P4$$word --backup MariaDB [(none)]> set password for 'test1'@'localhost'=password('P4ssword_'); [root@srv-gra2-mdb3 ~]# mariabackup --user=test1 --password=P4ssword_ --backup ?? | |
| Comment by Sylvain ARBAUDIE [ 2020-09-18 ] | |
|
i cannot reproduce with @ neither with #. only $ seem to be an issue. | |
| Comment by Elena Stepanova [ 2020-09-21 ] | |
|
Did you try to connect as
(note the quote marks around the password)? | |
| Comment by Sylvain ARBAUDIE [ 2020-09-21 ] | |
|
i'll try and test that asap | |
| Comment by Sylvain ARBAUDIE [ 2020-09-23 ] | |
|
Ok. Using the simple quotes around the password is working. i guess we can close this issue again. |