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 cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
No comments:
Post a Comment