How can I enable full file protection (encryption) on iOS for SQLite databases?
The obvious, easy part is setting the NSFileProtectionComplete attribute on the SQLite database file after it's first created. Presumably this attribute will stick, because I don't think SQLite every recreates the file from scratch, it just updates it incrementally. The problem is the side files created by SQLite. By default there is a "journal" file that exists temporarily during transactions, and if one enables the write-ahead log (WAL) feature, which really improves write performance, there are about three side files that seem to exist permanently, which contain recently-added rows before they get merged into the main database file. How do I ensure that those files get the appropriate protection attributes too? —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
