It is really hard to describe all the project in few e-mails.
Obviously, we will not try to run entire database software in that
secure hardware. Also memory limitations are not important.
For example, please check the research on "oblivious RAM" to see even
small memory on such hardware can be l
Our basic claim is to be able to do most of the encryption while we are
reading the page. That is the reason I need the threads. Any suggestion
about the threads are welcome. Thanks.
Murat
Alvaro Herrera wrote:
On Fri, Sep 10, 2004 at 11:
Murat Kantarcioglu <[EMAIL PROTECTED]> writes:
> This piece will be a part of a bigger design and the problems
> mentioned are very real. In the future, our goal is to design a database
> system where the processing is done in a "secure coprocessor"(i.e no one
> will be able to see what is inside)
On Fri, Sep 10, 2004 at 11:52:26AM -0500, Murat Kantarcioglu wrote:
> Can you suggest me a solution to how to do
> this on Postgresql backend?
>
> I am asssuming that somewhere in the code, you are calling a function like
> getPage(Page_id)
> to retrieve the page(I am trying to change backen
Thanks for the comments.
This piece will be a part of a bigger design and the problems
mentioned are very real. In the future, our goal is to design a database
system where the processing is done in a "secure coprocessor"(i.e no one
will be able to see what is inside) and
the small code inside the
