Ann W. Harrison wrote:

>Mitchell Peek wrote:
>
>
>If there were an easy answer to that question, Firebird would do
>encryption itself. The hard problem is key management. No doubt
>the public/private key pair algorithms are a solution - though I
>haven't seen exactly how it would work.
>

And basically, was the heart of my question.

>A third problem is indexing - if the encrypted data doesn't sort the same way
>as non-encrypted data (and it won't), range retrievals won't
>work.
>
>

Had already considered this, but I have a workaround for those issues.

I suppose the best method is to implement in a middle tier "trigger"
rather then have the DB have any part of it, beyond storage, that is.

Thanks,
Mitch