David Maass wrote:
unfortunately the "encrypt database" feature is a bit expensive for a freeware fun project, are there other ways to prevent ppl from reading the database? What about using a cryptoAPI (for example the microsoft one), and do some symetric encryption in the program before storing the data in the database. The problem: you have to compile the key into your program - not that optimal too, but better than nothing I think.
If you're worried about other users not the originator of the data, file permissions are favorite to keep them out of things that aren't theirs. If you're worried about valid users who shouldn't see data in a shared database, then encryption is best.
For a project of mine that required user password to be stored in a shared SQLite database I stored passwords as md5 chcksums. The rest of the data I left alone, since it wasn't information that needed to be kept secret.
Clay
