Timeline for Best practice for securing encrypted content on Android app
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2016 at 9:16 | comment | added | Darriuk | I agree I could use a password derived key that gets sent securely to the server, which then encrypts the content and returns the encrypted content file to the app. Some problems with that: 1) I would prefer to pre-encrypt the content, 2) in terms of UX I'd really rather avoid the password step, and 3) that's a big processing overhead for the server. I've edited the original question with this in mind. | |
| Sep 16, 2016 at 9:12 | comment | added | chichilatte | Are you saying... * the user would provide their secret * the server would encrypt the content using that secret and send the encrypted content to the user * the user can then view the content whenever they supply their secret ? | |
| Sep 15, 2016 at 14:07 | review | First posts | |||
| Sep 15, 2016 at 16:02 | |||||
| Sep 15, 2016 at 14:02 | history | answered | kreynolds | CC BY-SA 3.0 |