On Apr 17, 2009, at 10:17 AM, Stefan Langwald wrote:
MySQLs own Function AES_(EN|DE)CRYPT is pretty cool for this case.
--
Stefan Langwald
We use MySQL's AES_(EN|DE)CRYPT. It's fast, easy to use and uses 128
bit encryption (optionally 256).
http://dev.mysql.com/doc/refman/5.1/en/encryptio
On Fri, Apr 17, 2009 at 10:15 AM, דניאל דנון wrote:
> If its by a user-basis, something that can be a bit risky but possible -
> You
> can encrypt it, password is hashed on database, and the key to the other
> data is the un-encrypted password..
>
> On Fri, Apr 17, 2009 at 5:00 PM, Russell Jones
MySQLs own Function AES_(EN|DE)CRYPT is pretty cool for this case.
--
Stefan Langwald
2009/4/17 דניאל דנון :
> If its by a user-basis, something that can be a bit risky but possible - You
> can encrypt it, password is hashed on database, and the key to the other
> data is the un-encrypted passw
If its by a user-basis, something that can be a bit risky but possible - You
can encrypt it, password is hashed on database, and the key to the other
data is the un-encrypted password..
On Fri, Apr 17, 2009 at 5:00 PM, Russell Jones wrote:
> We are looking at a project where we will potentially
At 10:00 AM -0400 4/17/09, Russell Jones wrote:
We are looking at a project where we will potentially need to store
sensetive information in a few fields of a MySQL table. Any recommendations
on where to look for best practices in doing this? for encrypting the data,
etc.? We will need to be able
We are looking at a project where we will potentially need to store
sensetive information in a few fields of a MySQL table. Any recommendations
on where to look for best practices in doing this? for encrypting the data,
etc.? We will need to be able to decrypt the data as well, although this can
pr
6 matches
Mail list logo
