Skip to content

Commit

Permalink
updates to the distribution
Browse files Browse the repository at this point in the history
  • Loading branch information
n8fr8 committed Nov 29, 2011
1 parent a5f0752 commit 8cdfd18
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 6 deletions.
16 changes: 10 additions & 6 deletions dist/SQLCipherForAndroid-SDK/README
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@

SQLCipher for Android v1 (0.0.6-RC1)
2011/10/29
SQLCipher for Android v1 (0.0.6-FINAL)
2011/11/29

CHANGELOG
- includes icu44 data file for devices without it built-in ( < 2.2)
Expand All @@ -18,19 +18,23 @@ Android 2.3.3 (SDK Level 10)
Android 3.0 (SDK Level 11)
Android 3.1 (SDK Level 12)
Android 3.2 (SDK Level 13)
Android 4.0 (Not Tested)

HOW TO

1) Update your import path from android.database to info.guardianproject.database and you are almost there!
1) copy the libs folder into your project. If you are targeting 2.2 and below, include the 'icudt44l.zip' in the assets folder as well.

2) then when you open your database, just pass a variable argument to the open database method with your password:
2) Update your import path from android.database to info.guardianproject.database and you are almost there!

3) then when you open your database, just pass a variable argument to the open database method with your password:

SQLiteDatabase.loadLibs(this); //first init the db libraries with the context
SQLiteOpenHelper.getWritableDatabase("thisismysecret"):

and you are secured!
4) run your app to ensure all the libraries are being loaded correctly, and that your app runs.

You will need to implement a passcode entry user interface to your application, as well. The longer the passcode, the better.
5) You will need to implement a passcode entry user interface to your application, as well.
The longer the passcode, the better.

ABOUT

Expand Down
Binary file modified dist/SQLCipherForAndroid-SDK/libs/sqlcipher.jar
Binary file not shown.

0 comments on commit 8cdfd18

Please sign in to comment.