android-database-sqlcipher alternatives and similar packages
Based on the "ORM" category
An Android helper class to manage database creation and version management using an application's raw asset files
Lightweight, embedded, syncable NoSQL database engine for Android.
Android library for auto generating SQL schema and Content provider
A Java library to manage bean's persistence in SQLite, SharedPreferences, JSON, XML, Properties, Yaml, CBOR. For Java and Android platform
A wrapper to replicate android's SQLiteDatabase with restoring capability.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of android-database-sqlcipher or a related project?
Download Source and Binaries
SQLCipher for Android runs on Android 4.1–Android 10, for
We welcome contributions, to contribute to SQLCipher for Android, a contributor agreement needs to be submitted. All submissions should be based on the
An Illustrative Terminal Listing
A typical SQLite database in unencrypted, and visually parseable even as encoded text. The following example shows the difference between hexdumps of a standard SQLite database and one implementing SQLCipher.
~ sjlombardo$ hexdump -C sqlite.db 00000000 53 51 4c 69 74 65 20 66 6f 72 6d 61 74 20 33 00 |SQLite format 3.| … 000003c0 65 74 32 74 32 03 43 52 45 41 54 45 20 54 41 42 |et2t2.CREATE TAB| 000003d0 4c 45 20 74 32 28 61 2c 62 29 24 01 06 17 11 11 |LE t2(a,b)$…..| … 000007e0 20 74 68 65 20 73 68 6f 77 15 01 03 01 2f 01 6f | the show…./.o| 000007f0 6e 65 20 66 6f 72 20 74 68 65 20 6d 6f 6e 65 79 |ne for the money| ~ $ sqlite3 sqlcipher.db sqlite> PRAGMA KEY=’test123′; sqlite> CREATE TABLE t1(a,b); sqlite> INSERT INTO t1(a,b) VALUES (‘one for the money’, ‘two for the show’); sqlite> .quit ~ $ hexdump -C sqlcipher.db 00000000 84 d1 36 18 eb b5 82 90 c4 70 0d ee 43 cb 61 87 |.?6.?..?p.?C?a.| 00000010 91 42 3c cd 55 24 ab c6 c4 1d c6 67 b4 e3 96 bb |.B?..?| 00000bf0 8e 99 ee 28 23 43 ab a4 97 cd 63 42 8a 8e 7c c6 |..?(#C??.?cB..|?| ~ $ sqlite3 sqlcipher.db sqlite> SELECT * FROM t1; Error: file is encrypted or is not a database
(example courtesy of SQLCipher)
You have a two main options for using SQLCipher for Android in your app:
Using it with Room or other consumers of the
Using the native SQLCipher for Android classes
In both cases, you will need to add a dependency on
such as having the following line in your module's
implementation "net.zetetic:android-database-sqlcipher:4.4.0" implementation "androidx.sqlite:sqlite:2.0.1"
4.4.0 with the version you want)
Using SQLCipher for Android With Room
SQLCipher for Android has a
SupportFactory class in the
that can be used to configure Room to use SQLCipher for Android.
There are three
SupportFactory(byte passphrase, SQLiteDatabaseHook hook)
SupportFactory(byte passphrase, SQLiteDatabaseHook hook, boolean clearPassphrase)
All three take a
byte to use as the passphrase (if you have a
SQLiteDatabase.getBytes() to get a suitable
byte to use).
Two offer a
SQLiteDatabaseHook parameter that you can use
for executing SQL statements before or after the passphrase is used to key
The three-parameter constructor also offers
clearPassphrase, which defaults
true in the other two constructors. If
clearPassphrase is set to
this will zero out the bytes of the
byte after we open the database. This
is safest from a security standpoint, but it does mean that the
instance is a single-use object. Attempting to reuse the
instance later will result in being unable to open the database, because the
passphrase will be wrong. If you think that you might need to reuse the
SupportFactory instance, pass
Then, pass your
openHelperFactory() on your
final byte passphrase = SQLiteDatabase.getBytes(userEnteredPassphrase); final SupportFactory factory = new SupportFactory(passphrase); final SomeDatabase room = Room.databaseBuilder(activity, SomeDatabase.class, DB_NAME) .openHelperFactory(factory) .build();
Now, Room will make all of its database requests using SQLCipher for Android instead of the framework copy of SQLCipher.
SupportFactory should work with other consumers of the
Room is merely a prominent example.
Using SQLCipher for Android's Native API
If you have existing SQLite code using classes like
converting your code to use SQLCipher for Android mostly is a three-step process:
importstatements with ones that use
Before attempting to open a database, call
SQLiteDatabase.loadLibs(), passing in a
Context(e.g., add this to
Applicationsubclass, using the
Applicationitself as the
When opening a database (e.g.,
SQLiteDatabase.openOrCreateDatabase()), pass in the passphrase as a
The rest of your code may not need any changes.
An article covering both integration of SQLCipher into an Android application as well as building the source can be found here.
In order to build
android-database-sqlcipher from source you will need both the Android SDK, Gradle, and the Android NDK. We currently recommend using Android NDK version
r20. To complete the
make command, the
ANDROID_NDK_HOME environment variable must be defined which should point to your NDK root. Once you have cloned the repo, change directory into the root of the repository and run the following commands:
# this only needs to be done once make init # to build the source for debug: make build-debug # or for a release build: make build-release
The Android support libraries are licensed under Apache 2.0, in line with the Android OS code on which they are based. The SQLCipher code itself is licensed under a BSD-style license from Zetetic LLC. Finally, the original SQLite code itself is in the public domain.
*Note that all licence references and agreements mentioned in the android-database-sqlcipher README section above are relevant to that project's source code only.