Yeah its coming back non-encrypted, thanks for the heads up, do you know how i would apply just sha1 encryption to it from there?
On Jul 28, 6:17 am, Andras Kende <[email protected]> wrote: > Yes, its overwrites cake's hashPassword function to not to salt the > password put the code into usually user model > and see if the password is encrypted in the debug display... > > Andras > > On Jul 27, 2009, at 4:52 PM, Steppio wrote: > > > > > @Miles J, thanks for the post but im using alot of cookies so i need > > the salt value set in core, just not used in the authentication > > process. > > > @Andras Kende, thanks mate, do you know what it does? > > > On Jul 27, 9:14 pm, Andras Kende <[email protected]> wrote: > >> Hello, > > >> You could try in your model: > > >> function hashPasswords($data){ > >> return $data; > >> } > > >> Andras > > >> On Jul 27, 2009, at 1:53 PM, Steppio wrote: > > >>> Hi there, > >>> I was wondering if anybody knows a way to bypass the salting that > >>> the > >>> Security component automatically gives to a password? > > >>> The problem is that i have a database of old passwords and im > >>> converting the site into a CakePHP site, however when im trying to > >>> log > >>> in to the new site the password being returned by the debugger > >>> appears > >>> to have been salted and therefore doesnt conform to my original, > >>> non- > >>> salted sha1 password. > > >>> Any help would be greatly appreciated. > > >>> Thank you! > > >>> Steppio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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?hl=en -~----------~----~----~----~------~----~------~--~---
