Re: php 4.x + mysql 5
| From: | Nathan Rixham | Date: | Sat, 09 Feb 2008 18:45:27 +0000 |
| Subject: | Re: php 4.x + mysql 5 | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-269008@lists.php.net to get a copy of this message | ||
save passwords as sha2 or such like instead?
further, it would appear that since the "old password" "new password" is set mysql server side, then php will have no bearing what so ever on how passwords are saved, seeing as it's mysql which will run the password() function and not php :)
ps too bad on the ol php 4 job
Nathan
ahlist wrote:
On Feb 8, 2008 4:16 PM, Jim Lucas <lists@cmsws.com> wrote:ahlist wrote:Good idea! I may end up doing that. My goal is to position this so that a move to php5 would work and not be stuck with a bunch of old-style mysql passwords that need updated by users (since the original passwords are not retrievable of course for conversion unless I store plain text copies, which I do not want to do). Thanks for your input.Hi, I have a clean php 4.4.7 compile but it still shows the old mysql lib version. I can't find where it is picking that up at. Is it just built into the php sources that way?Yes, it is included with the php source. If you want it to use newer libs, then download the devel packages for the newer mysql version and at compile time, point the configure script for php use the newer devel libs instead. That should be all that is needed.