Timeline for Encrypt data stored in a database
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2015 at 3:36 | comment | added | Neil Smithline |
Depending on the exact meaning of encrypted in a way that only the user will be able to access it, moving encryption to the client may be overkill. Perhaps that means that the (server) app never sees the data in clear-text but it may also mean that the app can't access the data without the user's password.
|
|
| Aug 14, 2015 at 13:23 | comment | added | gowenfawr | @PaulKertscher good point, I've updated the answer to address. | |
| Aug 14, 2015 at 13:23 | history | edited | gowenfawr | CC BY-SA 3.0 |
Addressed comment
|
| Aug 14, 2015 at 13:03 | comment | added | Paul K | You got some point. But this also implies that all en- and de-cryption has to be performed on the client, too, this in turn would move all code that's beyond basic CRUD to the client, since we could log the data too, if it's passed to and fro our classes. | |
| Aug 14, 2015 at 12:57 | history | answered | gowenfawr | CC BY-SA 3.0 |