Timeline for Options for client-side encryption of local web databases
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Feb 12, 2016 at 13:44 | history | suggested | Rory McCune | CC BY-SA 3.0 |
I'm fairly sure OP didn't mean SHA-256 which is a hashing algorithm and not used for encryption. They most likely meant AES-256
|
| Feb 12, 2016 at 10:11 | review | Suggested edits | |||
| S Feb 12, 2016 at 13:44 | |||||
| Mar 25, 2014 at 8:58 | vote | accept | Adam Marshall | ||
| Mar 21, 2014 at 13:48 | history | bounty awarded | Adam Marshall | ||
| Mar 17, 2014 at 15:38 | comment | added | Michael Shaw | I doubt you can achieve this as a web application... we solved it as a combination of native app, and central server using a SOAP web service. doing the web services as REST is probably more sensible these days, but you will need to think about the client certificate generation bit carefully | |
| Mar 17, 2014 at 13:51 | comment | added | Adam Marshall | Some really good pointers here, thank you. Number 2 is of particular interest - where did you store the data? Was it a web app or a hybrid or a native app? I'm not sure what device specific information I could access from a web application, obviously a Phonegap application would have access to IMEI, etc. Any recommended resources when conducting your security analysis? | |
| Mar 17, 2014 at 13:10 | history | answered | Michael Shaw | CC BY-SA 3.0 |