Pardon the previous cryptic reply (!). The Blowfish algorithm is more secure than the Security::cipher() method. In most cases, if you or your client are overly concerned with data security, then Blowfish (or its successor, Twofish) are both viable options for encryption/decryption schemes. There are dozens of other algorithms as well, but people tend to cling to their preferred cipher algorithms religiously; I'm more of an agnostic ;-)
In general, if data security is extremely important for you, I would recommend hiring a specialized consultant to analyze your workflow and security measures. There are far more important things to consider than the strength of the encryption algorithm used. Just my Mg== cents. -Joel. On Jun 15, 3:37 am, seedifferently <[EMAIL PROTECTED]> wrote: > > From cold hard facts, no. > > Joel, please forgive me but I'm a little confused by your answer. > > Quite simply, is Security::cipher() a viable alternative to > mcrypt_encrypt or would it be more advisable to go the route of > mcrypt_encrypt for sensitive data in CakePHP? I have seen a helper/ > component for mcrypt in the bakery. Would you recommend that over > Security::cipher() or are they both going to be about the same > considering that no encryption method is absolutely bulletproof? > > Thanks, > Seth --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
