On Mar 11, 2006, at 2:04 PM, Michael Williams wrote:
I think for my purposes simply encrypting the DATABASE itself would
be better. Basically the only encrypted database will be one of
serial numbers and preferences. I don't really want to go through
the trouble of converting/encrypting each individual entry; not to
mention managing a seperate array. I realize that the DB would be
decrypted while working, but it would only be referenced for very
very very short periods of time at the beginning of any piece of
software's run to make sure they have a valid serial number, etc.
Any suggestions for this? If not, I'll still take any input you
have that would make your previously proposed method "easier". ;)
I do something similar. I read the encrypted database at startup (as
a binary stream), decrypt it in memory, write out the decrypted
database as a binary stream in a temp location and then access it
from there. When the app quits, the temp database is deleted. You
could also read in the new version, encrypt it, and write out the
newly encrypted file in the "default" location.
Christian
Pariahware, Inc. Custom Software
<[EMAIL PROTECTED]>
<http://www.pariahware.com>
--
God loved you so much that He gave His only son Jesus. What have you
done with God's gift?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
