![]() But the thing is there must be a place and time when those keys are revealed to decrypt data from database/storage. I was thinking about a simple solution to encrypt data using the non-shared key generated per user (to avoid decryption of the whole dataset using one key) and keeping those keys in some kind of vault. I need a solution to encrypt and protect data from leakage in case of unauthorized access to the machine(s) and/or application bug which can expose the data. Hey! I would like to create a feature in an existing application where users can keep very sensitive data. Via Ask HN: The way to encrypt and protect sensitive data in database The app itself is written in PHP, so I came to another idea to use ionCube or Zend Encoder to protect the file with cypher keys, but the question is: is it safe enough? ![]() ![]() ![]() I was thinking about a simple solution to encrypt data using the non-shared key generated per user (to avoid decryption of the whole dataset using one key) and keeping those keys in some kind of vault. NEW VERSION 1.1.0.0 WHIT IONCUBE DECODER INCLUDED UPDATE. Ask HN: The way to encrypt and protect sensitive data in database
0 Comments
Leave a Reply. |