Bug #43250 mysqlaccess doesn't handle special characters in password
Description:
If a password on the server includes special characters such as # or !, mysqlaccess cannot connect to the server.
How to repeat:
shell> mysql -uroot -p
Enter password:
mysql> set password=password('aaa###');
Query OK, 0 rows affected (0.05 sec)
shell> mysqlaccess mikiya test -Uroot -P
mysqlaccess Version 2.06, 20 Dec 2000
By RUG-AIV, by Yves Carlier (Yves.Carlier@rug.ac.be)
Changes by Steve Harvey (sgh@vex.net)
This software comes with ABSOLUTELY NO WARRANTY.
Unknown option: Uroot
Password for MySQL superuser :
Sorry,
An error occured when trying to connect to the database
with the grant-tables:
* Maybe YOU do not have READ-access to this database?
* If you used the -U option, you may have supplied an invalid username?
for the superuser?
* If you used the -U option, it may be possible you have to supply
a superuser-password to, with the -P option?
* If you used the -P option, you may have supplied an invalid password?
Suggested fix:
nada
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
Description: If a password on the server includes special characters such as # or !, mysqlaccess cannot connect to the server. How to repeat: shell> mysql -uroot -p Enter password: mysql> set password=password('aaa###'); Query OK, 0 rows affected (0.05 sec) shell> mysqlaccess mikiya test -Uroot -P mysqlaccess Version 2.06, 20 Dec 2000 By RUG-AIV, by Yves Carlier (Yves.Carlier@rug.ac.be) Changes by Steve Harvey (sgh@vex.net) This software comes with ABSOLUTELY NO WARRANTY. Unknown option: Uroot Password for MySQL superuser : Sorry, An error occured when trying to connect to the database with the grant-tables: * Maybe YOU do not have READ-access to this database? * If you used the -U option, you may have supplied an invalid username? for the superuser? * If you used the -U option, it may be possible you have to supply a superuser-password to, with the -P option? * If you used the -P option, you may have supplied an invalid password? Suggested fix: nada