You are so right. I generated the key on the server when I was investigating a secure means of storing the encryption keys. This was before I decided to not keep track of them. I couldn't find a cheap means of securing them. I investigated Gazzang but they were outside my budget. t intend to generate the key on the client before going to production.
On Wednesday, February 12, 2014 4:52:17 PM UTC-8, Jens Alfke wrote: > > > On Feb 12, 2014, at 4:28 PM, Alan McKean <[email protected] <javascript:>> > wrote: > > I'm using AES 128 encryption. The key is generated on my Node.js server > when the user registers to use the app. > > … > > I struggled with this as a business decision and finally decided I could > not safely/economically keep track of the encryption keys. User beware. > > > It sounds like the encryption/decryption is done only by the client, and > the server is simply passive storage of the encrypted documents? > But in that case, why create the encryption key on the server? By doing > that, you're no longer provably unable to read clients' documents. If you > changed the system to generate the key on the client (after all it's simply > generating a 128-bit random number) you could make better privacy > guarantees. > > Other than that, the system seems sound. > > —Jens > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/a8a1626a-62aa-4b02-a09d-b2bdb4b97d22%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
