Personally I handle such information as I would like my own information to be handled and that's secure as possible even for a small site/company etc etc. It's still personal information that in the wrong hands can do way to much damage.
On Nov 3, 4:54 pm, "euromark (munich)" <[email protected]> wrote: > yeah > i found 2 behaviours later on by searching with other filters > > but one question remains > how important would that be for a simple online shop? > > On 3 Nov., 12:45, WyriHaximus <[email protected]> wrote: > > > Did you take a look at this piece of > > code?http://bakery.cakephp.org/articles/view/cryptable-behavior > > > On Nov 3, 10:30 am, "euromark (munich)" <[email protected]> > > wrote: > > > > i was wondering how to save sensitive information of users > > > like cc number or bank data? > > > my guess is they should not be saved as plain "chars" but encrypted in > > > such a way that if the db is ever going to be hacked the retrieved > > > data would be useless to anyone without the correct "key" > > > > passwords usually are stored sha1-hashed as you dont intend to revert > > > that (and cant) > > > but with the above examples you need to > > > > is there some kind of behaviour to automatically cipher and save or > > > decrypt and read record data? > > > i stumpled uopn Security::cipher() for that matter > > > > and how save would that be? > > > could you re-build the original string from a given ciphered one with > > > a modern computer? or would it be pointless for "everyday hackers"? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
