Sequelpro: Do not include password flag if no password is specified

Created on 9 Nov 2013  路  5Comments  路  Source: sequelpro/sequelpro

Issue imported from Google Code: https://code.google.com/p/sequel-pro/issues/detail?id=1065
Reporter:[email protected] Date:2011-05-23 07:48:11 Status:WontFix Closed:2011-07-01

What steps will reproduce the problem?

  1. Connect to server over ssh connection (specify user/pass for ssh, only specify user for mysql - blank/empty password field)
  2. Get successful ssh connection, by get mysql error "Access denied for user 'root'@'localhost' (using password: NO)"
  3. If I use Terminal to ssh to the machine, and run "mysql" or "mysql -u root" I connect to the db just fine. If I run "mysql -u root -p" and provide a blank password (i.e. just hit return) then I get the same error as Sequel Pro gives me.

What is the expected output? What do you see instead?
I expect to connect without an error message.

I would expect that if no password is specified, then it would not use the "-p" flag or their would be a check box that differentiates between "no password" vs "blank password" (if there is a difference)

What version of Sequel Pro are you using? What version of MySQL are you
connecting to on the server?
I am using 0.9.8.1 (rev 2492), but I also confirmed this is still a problem with the latest nightly build (rev 3311)

MySQL version - 5.0.92-community-log

Please provide any additional information below.

Most helpful comment

I understand that this issue has been closed for a while, but it isn't fixed. I have exactly the same problem.

"mysql -u root" connects fine.
"mysql -u root -p" connects fine with a blank password.
Sequel Pro, with the password field left blank, fails to connect, throwing the error "MySQL said: Access denied for user 'root'@'localhost'"

MariaDB 10.1.22 and Sequel Pro 1.1.2

All 5 comments

Author:[email protected] Date:2011-05-28 03:50:51

AFAIK a blank password an no password are handled the same.

I think the server has the actual password stored in it's my.cnf file
That way you can login on the server to mysql without giving an explicit password.

However Sequel Pro will never use the my.cnf files on a remote host.

Author:[email protected] Date:2011-05-29 08:39:22

I thought the same as schlabberdog, but having looked into this a bit further there may actually be very subtle differences. We don't do anything quite like the command-line switch you mention, but (having checked) we do pass an empty string into a MySQL library function call, instead of passing in a NULL.

I don't think this _should_ affect anything, but the MySQL manual does explicitly mention a couple of optimisations for NULL, and it seems neater; so r3314 ensures NULL is used for blank MySQL passwords.

Author:stuart02 Date:2011-07-02 11:16:29

Closing after no further feedback.

I understand that this issue has been closed for a while, but it isn't fixed. I have exactly the same problem.

"mysql -u root" connects fine.
"mysql -u root -p" connects fine with a blank password.
Sequel Pro, with the password field left blank, fails to connect, throwing the error "MySQL said: Access denied for user 'root'@'localhost'"

MariaDB 10.1.22 and Sequel Pro 1.1.2

Please open a new issue. This issue has been closed since 2011!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sequelpro picture sequelpro  路  3Comments

guimadaleno picture guimadaleno  路  3Comments

gongmingqm10 picture gongmingqm10  路  3Comments

sequelpro picture sequelpro  路  4Comments

laoli4121 picture laoli4121  路  4Comments