On Mar 11, 2006, at 11:04 AM, Michael Williams wrote:
Ian,
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". ;)
Thanks so much,
Michael
The problem is that if you encrypt the entire FILE that is the database
you have to decrypt it to read it so you can use SQL to read it.
To do this, the database has to be in an unencrypted form for some
period of time.
At that point it could be copied and anyone could poke through it.
Having the API that DR Hipp provides stores the data in an encrypted
form and then but still eaves it searchable using regular SQL commands
_______________________________________________
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>
