
http://dev.mysql.com/doc/refman/5.7/en/password-hashing.html As part of routine maintenance I upgraded MySQL to a more recent version on the LUV server. Unfortunately I didn't test the system properly and didn't notice that Drupal was down. The problem was that the Drupal database was so old that it had a less secure method of storing the password that is rejected by newer versions of MySQL. The solution was to just set the password again to the same value (I don't think that the localhost connections used for MySQL access were at risk of leaking the password - and if they were we have bigger problems than Drupal data). Things should be fine now and the above URL is for anyone who is curious about the details or who is about to upgrade an old MySQL server. select Password from mysql.user; If the above command gives any results that are 16 bytes long then upgrading MySQL to a recent version will give you this issue. Finally please don't assume that I will read luv-ctte email in any reasonable amount of time for fixing the web site. Also don't assume that I will read personal email in such a quick time (although I will read it much sooner than mailing lists). There's the sysadmin@luv.asn.au address for reporting such things, etbe42@gmail.com for Google Hangouts, and you can email luv-ctte and ask someone to SMS me. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/

On 22/01/17 20:03, Russell Coker via luv-main wrote:
http://dev.mysql.com/doc/refman/5.7/en/password-hashing.html
As part of routine maintenance I upgraded MySQL to a more recent version on the LUV server. Unfortunately I didn't test the system properly and didn't notice that Drupal was down. The problem was that the Drupal database was so old that it had a less secure method of storing the password that is rejected by newer versions of MySQL.
Yikes! That is ancient. Glad you upgraded!
The solution was to just set the password again to the same value (I don't think that the localhost connections used for MySQL access were at risk of leaking the password - and if they were we have bigger problems than Drupal data).
Things should be fine now and the above URL is for anyone who is curious about the details or who is about to upgrade an old MySQL server.
Excellent, thanks for that. Cheers, Andrew
participants (2)
-
Andrew Pam
-
Russell Coker