oss-sec mailing list archives
Source of bad password hashing practices? MySQL manual...
From: Rich Felker <dalias () aerifal cx>
Date: Tue, 8 Oct 2013 19:57:52 -0400
It's come to my attention recently that the MySQL reference manual is recommending very poor password hashing practices as part of its security guidelines: "Do not store cleartext passwords in your database. If your computer becomes compromised, the intruder can take the full list of passwords and use them. Instead, use SHA2(), SHA1(), MD5(), or some other one-way hashing function and store the hash value." (http://dev.mysql.com/doc/refman/5.7/en/security-guidelines.html) With MySQL being one of the major traditional "LAMP stack" components, I wonder if this is the source from which many web developers are getting their ideas on how to do password hashing. What is the proper procedure for publicizing documentation bugs like this which are leading to poor security practice, and for getting them fixed? Rich
Current thread:
- Source of bad password hashing practices? MySQL manual... Rich Felker (Oct 08)
- Re: Source of bad password hashing practices? MySQL manual... gremlin (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... Alex Gaynor (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... Raphael Geissert (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... Seth Arnold (Oct 09)
- RE: Source of bad password hashing practices? MySQL manual... Christey, Steven M. (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... Chris Palmer (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... Kurt Seifried (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... Jeremy Stanley (Oct 09)
- RE: Source of bad password hashing practices? MySQL manual... Christey, Steven M. (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... gremlin (Oct 09)
- Re: Source of bad password hashing practices? MySQL manual... John Haxby (Nov 07)