Timeline for I need advice developing a sensitive data transfer/storage/encryption system
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2013 at 23:07 | comment | added | Morons | Al relational Dbs, mysql included a optimized to pull data by use of indexes.. I need to blog about this.. it comes up way too often | |
| Feb 21, 2013 at 22:56 | vote | accept | Matt Jadczak | ||
| Feb 21, 2013 at 23:34 | |||||
| Feb 21, 2013 at 22:56 | comment | added | Matt Jadczak | Honestly? I always thought MySQL was optimised for pulling data by primary key. For future reference, how could I store this data so this system scales to maybe over 100,000 users? Some sort of NoSQL? Switch away from PHP? | |
| Feb 21, 2013 at 22:53 | comment | added | Morons | For your scale. This will work.. | |
| Feb 21, 2013 at 22:51 | comment | added | Morons | Its not any easier to pull a record by id than to pull a file by name | |
| Feb 21, 2013 at 22:50 | comment | added | Matt Jadczak | Well, the main requirement is data security, speed comes second. The main "scaling factor" here will be user number - each user will only have 100-200 records, so decrypting that data block shouldn't be too bad. As for user number, that will hopefully scale with the MySQL, and if it goes over a few thousand, I guess I'll look at more efficient solutions then. | |
| Feb 21, 2013 at 22:49 | comment | added | Morons | I am saying to have one data file per user as oppos. To one recored.. you gain nothing by pushing all that data into a db | |
| Feb 21, 2013 at 22:46 | comment | added | Morons | Fyi: what you are doing here will never scale well. I think you need to qestion if this is really the requierment | |
| Feb 21, 2013 at 22:46 | comment | added | Matt Jadczak | Yes, all the data for the same user... What I wanted was a MySQL table with user id, data block for every user. | |
| Feb 21, 2013 at 22:44 | comment | added | Morons | To get the pk dosen't the user first have to click on the record he wants.. that means you need to first show him a record set... that means either displaying all the data or querying (reading) all the data.. that means decrypting all the data.... | |
| Feb 21, 2013 at 22:17 | comment | added | Matt Jadczak | Well, if I'll go with the block system, pulling the record out of DB by a primary key would be faster than searching a directory of thousands of files. As for the cookies, I'm thinking of re-setting the cookies on each page view, with a eg 10min expiry, so that after 10min inactivity a re-login is required. I need to store the decrypted key somewhere, else the user would have to enter their password on each page view. | |
| Feb 21, 2013 at 22:06 | history | answered | Morons | CC BY-SA 3.0 |