> On Jan 8, 2015, at 11:55 AM, Jsparrow <[email protected]> wrote: > > I see. I'll have to go with encryption then. The key can always be hardcoded > in the application anyway. Thanks for the assistance.
That's not secure! A hacker can very easily extract the key from the app and use it to decrypt anyone's database. (This sort of thing happens all the time, sadly.) It would be irresponsible of you to promise data security to your users and not actually deliver it. And depending on the specific situation and the country, it could be illegal. For example, if this were a healthcare related app to be used in the USA, you could be violating HIPAA regulations by providing insufficient data security. What exactly do you need the data security for, and what sorts of attacks are you trying to prevent? —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/8B5E7ABC-72CC-423E-8674-3A5E6EEC626D%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
