Ok, Androids, I have an odd question on SQLite's file storage.

We have a need to encrypt the data stored within SQLite.  The obvious
approach would be to encrypt individual records before storing them in
the table, but that will melt down.  For example, if we want to search
for a string, we would have to actually retrieve everything in the
table and decrypt all of it to find the string.  Doing a join seems
like it would be impossible.  We're not even going to explore or
consider that route.

I know that SQLite stores all the data in a single flat file.  I
assume that it accesses that file by MemoryMappedFile or something
like that.  My idea is to create a sub-class of MemoryMappedFile that
does block encryption / decryption on write / read.  Doing so would be
quite efficient, and lets us use SQLite as normal.  We would somehow
have to pass that special encrypted MemoryMappedFile to SQLite when
the instance is constructed.

But I've never done this before and don't really know any of these
internals.  Does anyone have some insight on where to begin on that?

Thanks

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to