0 results returned

[Gordiii]

0 results returned

[gavin-black]

Maybe I'm missing something, but how are you attempting to run sql queries? Encrypted Core Data uses standard core data calls to store and retrieve values. There shouldn't be any raw select statements you would be using on your end.

If you are just trying to look at the sqlite file using the sqlite3 CLI, then you need to make sure you have a version that supports ssl(Compile sqlcipher by hand and it should produce the proper executable to use) and set the pragma by hand (PRAGMA key=whatever).

[Gordiii]

Hello,

I'm not using any SQL queries directly but using the following core data calls in ViewDidLoad

....
AppDelegate* appDelegate = [AppDelegate sharedAppDelegate];
NSManagedObjectContext* moc = appDelegate.managedObjectContext;
NSEntityDescription *entityDescription = [NSEntityDescription entityForName:@Profile" inManagedObjectContext:moc];
NSFetchRequest *fetchRequest = [[NSFetchRequest alloc] init];
[fetchRequest setEntity:entityDescription];
profilesArray = [moc executeFetchRequest:fetchRequest error:nil];
NSLog(@"fetch count: %d", [profilesArray count]);

From the CLI, I am able to get results using sqlcipher:

$ ./sqlcipher encrypted.db
sqlite> PRAGMA KEY='myTestKey';
sqlite> SELECT COUNT(*) FROM ZPROFILE
1066

The SQL queries I listed in my last post was debug statements from the Xcode output window.

[gavin-black]

Hmmm, very odd. Sounds like it is storing it correctly, and your code seems fine. No errors getting buried in the console when you run your fetch request? Also if you run "strings encrypted.db" does it produce complete garbage? If it produces readable results something is wrong with the initial setup.

[Gordiii]

No errors getting buried in the console when you run your fetch request?

Nope

Also if you run "strings encrypted.db" does it produce complete garbage?

Yes, produce garbage such as:

84aw
??-B'?
8G;M1
+EXr6`
Sb-KS

I've isolated this into an independent small Xcode project. Would you like to take a look to see if you can spot anything? If so, here's the link:

https://dl.dropboxusercontent.com/u/1846743/TestSQLCipher.tar.gz

The sqlcipher.xcodeproj and openssl-xcode/openssl.xcodeproj references in the Xcode project for setting up "SQLCipher for iOS (http://sqlcipher.net/ios-tutorial/), were taken from https://github.com/sqlcipher/SQLCipherSpeed.git.

[gavin-black]

Thanks for the sample code, was able to get it running and it prints back 0 results as you described. Will try to track down where the issue is.

[Gordiii]

Cool. Just to note, from the command line, if you run:

./sqlcipher
sqlite> PRAGMA KEY='testkey';
sqlite> SELECT COUNT(*) FROM ZEATPROFILE

you should get 1066

[gavin-black]

Hmm for whatever reason I can't get PreloadUncover-Encrypted to decrypt. Can get all other encrypted dbs, including TestSQLCipher.sql, decrypted and read from them on command line. Any chance the key is wrong?

But actually I think the issue is where did PreloadUncover come from? You said it works with core-data, so did you take a working sqlite file generated from core-data, encrypt it by hand, and then use it? If so, encrypted-core-data isn't smart enough to automagically do the translation. Under the hood we are making our own sqlite tables and structures that are different to the existing core-data ones (Instead of reverse engineering Apple's layout, which in hindsight may have been smarter).

If that's the issue the work around would be to regenerate your structures programmatically. You can load up two controllers simultaneously, one for core-data and one for encrypted-core-data and should be able to fetch entities from one and save to the other. Not at all elegant, and there really should be migration code to ease the task, but should work.

[Gordiii]

did you take a working sqlite file generated from core-data, encrypt it by hand, and then use it?

Yes, spot on. I've got it to work now! Thanks very much for your prompt responses.

Although, I'm using SQLCipher version 3.7.17 as opposed to 3.8.0.2 which is in the Air:SQLCipherSpeed github project. The later was causing some issue, which I think I'm not going to put any effort into now.