Timeline for Recommendation for implementing encrypted MySQL database
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2018 at 15:53 | comment | added | Matthias | We decided to model the database correctly with no application-level encryption and instead use encryption outside on the disk level. Furthermore, as for replication safety, this was easily worked around in a different manner. | |
| Jan 19, 2018 at 15:52 | comment | added | Matthias | Thank you for your input. It became obvious that we were trying to solve two problems at once with not trusting the database with the knowledge of the original data. Or rather, what we tried to achieve was that we didn't trust the data in the databases that acted as replication/backup nodes in some instances. | |
| Nov 16, 2017 at 20:37 | history | answered | Benjamin Mord | CC BY-SA 3.0 |