OK - So why should I use ZeroDb when it seems to be using Crypt-DB for encrypted query processing [which is the USP of ZeroDb] when cryptDb is fully open source, free and verifiable?
Thank you for the clarification. How are you computing over encrypted data? From the "acknowledgements" section of the paper, it seems to be the same technique as cryptDB. If so, where is this source code? [I'm assuming this to be in C/C++] in the "crypto" folder as in cryptDb
No, we don't use any techniques from CryptDB at all. We thought about doing server-side set intersections using some ideas from CryptDB but we decided to not do that.
In brief, we don't compute on encrypted data, we search for encrypted data using encrypted indexes (which are operated from the client, even though are located remotely).
