Bug #400 Security problems with backslash
| Submitted: | 8 May 2003 10:53 | Modified: | 9 Mar 2005 18:52 |
|---|---|---|---|
| Reporter: | Peter Deacon | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Parser | Severity: | S4 (Feature request) |
| Version: | 4.1 | OS: | Windows (win32) |
| Assigned to: | CPU Architecture: | Any |
[8 May 2003 10:53]
Peter Deacon
[8 May 2003 11:33]
Peter Deacon
All backslash escape characters are ambiguous in the context of ODBC and should be removed from the ODBC interfaces.
[13 May 2003 23:36]
Michael Widenius
This is a bit hard to change as most MySQL clients assumes that one has to escape \ in MySQL strings. I have put on our todo in 4.1 to add an option to not espace things with \. The main problem is just to get the client mysql_escape_string() function to know when to escape and when to not escape strings.
[17 Dec 2004 2:33]
Ken Johanson
Looks like bug 6368 is a progess on this bug. I agree, only single quotes should need escaping, in keeping with ISO/ANSI rules, and that special backslash treatment will blindside developers who come from Oracle, Sybase, MS etc. Legacy client are not a concern for me; I intend to only run using the NO_BACKSLASH_ESCAPE mode, and hopefull the PreparedStatement side of JDBC/ODBC/etc drivers will be able to tell what mode the server's in (I personally use raw statements more often that PrpdStmts). And the php clients I have will have to be coerced into not using the escapecslashes function, in favor of a more standard escape function.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.052 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.