The master branch of the couchbase-lite-ios repo now includes optional on-disk database encryption. It uses SQLCipher (a variant of SQLite) to encrypt the database file, while attachments are individually encrypted with AES-256. Full instructions are on the wiki <https://github.com/couchbase/couchbase-lite-ios/wiki/Database-Encryption>.
This feature will be released in Couchbase Lite 1.1, but you can try it out now by checking out and building from the master branch. (Please note that the master branch already has other post-1.0.3 changes including an incompatible change to the file format <https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/mobile-couchbase/Hj7nG8SkFdk/5I2KkIE-bQUJ>.) We’d love to get feedback from you. It’s pretty easy to adopt if you also use the available CBLEncryptionController class, which is a utility that runs the user interaction to prompt for passwords. It will even use Touch ID, if available, to store a randomly-generated AES key, so the user doesn’t need a password at all. (I can say from experience that using your thumbprint to unlock your app’s database is pretty cool. I’m storing all of my missile launch codes and international money laundering paperwork in Couchbase Lite now.) We don’t expect most developers to use this feature — the iOS filesystem is already pretty well encrypted — but there are apps for which such encryption is a requirement (often due to health-care or banking laws, or corporate policies) so this feature has been a blocker for some people. (Yes, encryption is coming to our other platforms as well.) —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/177A3F4A-92C9-49F1-A1BC-80F4412956AE%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
