From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Murat Kantarcioglu <kanmurat(at)cs(dot)purdue(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Supporting Encryption in Postgresql |
Date: | 2004-09-09 21:39:54 |
Message-ID: | 1094765993.2582.2.camel@fuji.krosing.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On R, 2004-09-10 at 00:03, Murat Kantarcioglu wrote:
> My questions are in order to support page level encryption(i,e encrypt
> each page before writing back to disk and decrypt each page after we
> read from disk.) which parts of the code should be changed?
> Our more simply, is /src/backend/storage/smgr/md.c the only code
> that does the disk access?
>
> Since our design requires thread support (we will do some of the
> decryption, before we see the data, therefore during disk access, we
> need to continue decryption)
Why do you think that you need threads to do the (en/de)cryption?
Why is it not sufficient to just replace the page read/write functions
with ones supporting encryption ?
Or just use encrypted filesystem ;) <evil grin>
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-09-09 21:40:41 | Re: Clarification of action on Delete |
Previous Message | Simon Riggs | 2004-09-09 21:30:27 | Clarification of action on Delete |