RE: Possible Bug in mysql 3.23.38

2001-06-16 Thread William M. Quarles
I would like to note that bug reports should only be sent out if you are using the latest version, which now is 3.23.39. --On Friday, June 15, 2001 17:37 -0600 Chris Bolt [EMAIL PROTECTED] wrote: After creating a new database, I ran: update user set password = 'SomeJunk' where user =

Possible Bug in mysql 3.23.38

2001-06-15 Thread Simon Shapiro
Could not find a bug report form. So I am telling y'll... Platform: FreeBSD 4.3 (I do not think it matters) After creating a new database, I ran: update user set password = 'SomeJunk' where user = 'root'; This inserts the string 'SomeJunk' literally into the database, unencrypted. This is

Re: Possible Bug in mysql 3.23.38

2001-06-15 Thread Joshua J. Kugler
PLEASE read the manual. you need to set password = password('SomeJunk') And the bug report form can be obtained by running mysqlbug, the instructions for which are also found in the manual. Thank you. j- k- On Friday 15 June 2001 13:08, Simon Shapiro wrote: Could not find a bug

RE: Possible Bug in mysql 3.23.38

2001-06-15 Thread Chris Bolt
After creating a new database, I ran: update user set password = 'SomeJunk' where user = 'root'; This inserts the string 'SomeJunk' literally into the database, unencrypted. This is SQL expected but the result is a database lockout (not to mention the security breach of having the clear

Re: Possible Bug in mysql 3.23.38

2001-06-15 Thread Benjamin Pflugmann
Hello Simon. On Fri, Jun 15, 2001 at 05:08:18PM -0400, [EMAIL PROTECTED] wrote: Could not find a bug report form. So I am telling y'll... Platform: FreeBSD 4.3 (I do not think it matters) After creating a new database, I ran: update user set password = 'SomeJunk' where user = 'root';