Thanks for the link. Unfortunatly its a little expensive and probably 50% 
slower than my implementation. 

No offense, but C is a language that a lot of us tolerate and is not the 
panacea that some C developers like to believe it is. Reading C is like reading 
Chinese. ASM may not be a high level language, but it certainly is fast.

My knowledge of encryption is above adequate, while I will be the first to 
admit my understanding of the inner workings of a database is not. As I grapple 
to understand how Encryption may be applied to a database project I am 
developing, I have displayed my ignorance in the hope of learning. It is fairly 
obvious that some very talented developers on this forum would prefer to use 
this as an exercise in pedantic sniping rather than offer substantive help.

To the others, I thank you.

Cory Nelson <[EMAIL PROTECTED]> wrote: On Mon, Aug 25, 2008 at 6:33 PM, Derek 
> Dennis thank you for taking the time to explain that. I have read the 
> Architecture page and I think I have a better idea.
> Since this does seem to be a viable way to protect the data I would like to 
> implement the schema, but using AES instead of MD5 which is unsecure.
> Has anyone done this and posted the code?

drh sells a version with encryption builtin here:

I don't mean any offense here, but in case you aren't doing this to
learn and will really be storing people's credit cards and socials:
you are not knowledgeable enough in this area to be writing any
production encryption code.  Doing so would be a disservice to any
customers.  Definitely use available tested code in this case, like
drh's version.

Cory Nelson
sqlite-users mailing list

sqlite-users mailing list

Reply via email to