Skip to main content

SQLCipher Working But Incorrect Password



I've just implemented SQLCipher in my app to encrypt one fairly simple database. I followed all of the setup instructions carefully on this tutorial and the project is building and the app is running successfully. However, when I use their sample code to encrypt my database, my password is somehow incorrect and I am now unable to open my database. Here is the code:







NSString *path = [[NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES) objectAtIndex:0]

stringByAppendingPathComponent: @"dict.sqlite"];

if (sqlite3_open([path UTF8String], &database) == SQLITE_OK) {

const char* key = [@"BIGSecret" UTF8String];

sqlite3_key(database, key, strlen(key));

if (sqlite3_exec(database, (const char*) "SELECT count(*) FROM sqlite_master;", NULL, NULL, NULL) == SQLITE_OK) {

// password is correct, or, database has been initialized

NSLog(@"Correct Password :)");

}

else {

// incorrect password!

NSLog(@"Incorrect Password :(");

}

}

else {

sqlite3_close(database);

NSAssert1(NO, @"Failed to open database with message '%s'.", sqlite3_errmsg(database));

}

}







sqlite3 *database; is declared in my interface. My app is crashing on this line:







if (sqlite3_prepare_v2(database, sql, -1, &init_statement, NULL) != SQLITE_OK) {

NSAssert1(NO, @"Error: failed to prepare statement with message '%s'.", sqlite3_errmsg(database));

}







Everything worked just fine without the encryption, so there is no issue with the rest of my code. The console prints "Incorrect Password :(" before the crash. The crash log is: Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Error: failed to prepare statement with message 'file is encrypted or is not a database'.' There is clearly an issue with the password. Any help?





Thanks.


Comments

  1. The most likely problem is that you are trying to set a key on an existing database that is not already encrypted, dict.sqlite. The sqlite3_key function does not encrypt an existing database. If you want to encrypt an existing database you'd either need to ATTACH a new encrypted database and move data between the two, as described here:

    http://zetetic.net/blog/2009/12/29/how-to-encrypt-a-plaintext-sqlite-database-to-use-sqlcipher/

    Or, using the SQLCipher 2 you can use sqlcipher_export which provides an easy way to move data between databases.:

    http://groups.google.com/group/sqlcipher/msg/76d5b03426419761

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex