| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | David Blewett <david(at)dawninglight(dot)net>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Page-Level Encryption |
| Date: | 2006-01-20 20:44:59 |
| Message-ID: | 43D14BCB.9030304@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> IF they've got root, and the unencrypted data or the password / key is
> on the machine or in memory on it, you've lost. It may make it harder
> for them to get it, but they can.
>
This is true but in answer to your question you can use something like
cryptfs. Note that you will loose performance.
Joshua D. Drake
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl - http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Blewett | 2006-01-20 20:47:04 | Re: Page-Level Encryption |
| Previous Message | Scott Marlowe | 2006-01-20 20:37:19 | Re: Page-Level Encryption |