Encryption Indeed
Thank you for all the responses!
Unfortunately I still feel stuck.
That would be "encryption".
Encryption was in fact the first thing I looked up. I eventually found a bread crumb trail left by Apple that seemed promising until I started finding lines like this one (found in
TypesSecVuln.html )
"The problem of how to protect a vendor's data from being copied or used without permission is not addressed here."
I continued down the path any way and found the
Certificate, Key, and Trust Services Reference. This however is obviously intended to be used as a way to encrypt the user's data not vendor's data. I may be able to get it to "keep the kid sister out of the club house" but I figure that the less I do, pushing round pegs into square holes, the more secure the data will actually be. ghayenga and jnic are together right on here:
If you're including them as resources than anyone can open the backup and the app bundle and find your files. To make them unreadable you need to encrypt them and have your app decrypt them before it uses them.
the best you can hope to do is make it prohibitively difficult so that none of your users invest the time to defeat it.
In this case, a user could load your running app into a debugger and extract the decryption key from memory.
So I'm looking for something that is actually intended for this purpose.
My searches continue to reveal ways to encrypt the user's data.
Still looking - Please help
- Joshua