| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bob <luckyratfoot(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Matt McNeil <mcneil(at)callahanpro(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Transparent encryption in PostgreSQL? |
| Date: | 2005-07-14 00:05:17 |
| Message-ID: | 200507140005.j6E05H317532@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Bob <luckyratfoot(at)gmail(dot)com> writes:
> > Doesn't that really only save you from having someone come in at the OS
> > level and copying your data files and than moutning them on a differet
> > server/database. A person could still come in to psql as a dba or anyone for
> > that matter with the proper select grants and query off that data and see it
> > in encrypted.
>
> Yeah, the real question here is what threats are you trying to defend
> against. "I need an encrypted database" is pretty nearly a meaningless
> statement --- first tell us who the attacker is that you're worried about.
We have an encryption section in the documentation now --- please see
that.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Mitchell | 2005-07-14 00:09:49 | Stopping Postgres |
| Previous Message | Bruce Momjian | 2005-07-13 23:52:04 | Re: Converting MySQL tinyint to PostgreSQL |