Bug #16178 Parse Password - Unable to Connect

Submitted:	4 Jan 2006 8:13	Modified:	3 Dec 2007 7:28
Reporter:	Henrik Binggl	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Windows (Win XP)
Assigned to:	Jess Balint	CPU Architecture:	Any

Description:
Unable to connect if password contains "special" chars.
e.g. #@ZU34;_

Only ODBC Driver is affected, "normal" connections with Client or MySQL-Admin
work.

MyODBC 3.51.12
MySQL    4.1.12 - RHEL 4.0

How to repeat:
Use "special" chars in password
e.g. #@ZU34;_

Suggested fix:
Handle "special" chars correctyl.

I noticed that the 'special character' which makes MyODBC to fails
is the semicolon ;. However the mysql client accepts.

http://bugs.mysql.com/bug.php?id=29572 is a duplicate of this.

Jess looked into this a little bit, and it looked like the driver manager was screwing this up.

Perhaps we should store the password in the DSN as a hex-encoded string, or something clever like that.

Fixing this is going to require too many code changes to do in the 3.51 series. We'll get to it for the next major release.

Bug #31028 was marked as a duplicate of this bug.

Bug #31007 is marked as duplicate of this bug

Bug #22298 is a duplicate of this bug here.

Fixed handling of semi-colon in escaped values.

bugfix

Attachment: bug16178.diff (application/octet-stream, text), 1.15 KiB.

Fix committed in rev853, will be released in 5.1.1.

A note has been added to the 5.1.1 changelog: 

Connector/ODBC would fail to connect to the server if the password contained certain characters, including the semicolon and other punctuation marks.

Page generated in 0.070 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.