I see. I'll have to go with encryption then. The key can always be hardcoded in the application anyway. Thanks for the assistance.
On Thursday, January 8, 2015 7:34:59 AM UTC, Jens Alfke wrote: > > > > On Jan 7, 2015, at 6:38 PM, Jsparrow <[email protected] <javascript:>> > wrote: > > > > No I don't mean encryption, I'm talking about having database > credentials. For example, with MySQL you have database credentials and you > can't access the database without providing the database username and > password when you open the connection to the database. > > MySQL is a server, so it can use a login to enforce access. But with an > embedded database you have access to the raw data files, so the only way to > protect them from being read (or modified) is to encrypt them. It's like > trying to protect a text file or a Word doc from being read -- you have to > encrypt it. > > And encryption means a key that has to be kept secret, which means the > user has to enter it as a passphrase when the app launches. > > --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/ed4af034-65cf-4399-b7e1-a4cf187d0cb5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
