Chris Lamb wrote: > But what if your plaintext password looks like a valid MD5 string?
Hi Chris, Indeed then the code would cause a problem in this case. I don't think that any of the places I've used it would accept an MD5 as a password, and as such the MD5 and password validations are mutually exclusive - but if that is not the case then it would be necessary to take that into account when saving the user info. The ONLY reason to require a check of any kind before md5ing is if it is possible to edit an MD5ed field, if there is no possibility to edit the field, there is no risk to md5 what was saved when the object was created and the code can be simplified to a simple md5 statement (as icelander probably put in place). Don't scaffold a view for the admin to view the users if this is the case ;). Cheers, AD7six --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
