pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Zvi Fer <zferentz@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres security issue - protecting datafiles
Date: Tue, 10 Jun 2008 10:22:35 +0300
Message-ID: <96f635390806100022o11e0d033v782ff30c56391778@mail.gmail.com> (raw)
In-Reply-To: <25650.1212595910@sss.pgh.pa.us>
References: <ce1722a1-ab34-4915-b5db-1915c0dfa5b0@f63g2000hsf.googlegroups.com>
	<25650.1212595910@sss.pgh.pa.us>

Thnx for the input.

I have another solution, which i tried to avoid : my company provides
file/folder-level encryption . i can apply this encryption with specific
configuration for the postgres processes . this way - even the root cannot
access the data, the only one that can access the database-files is the
owner of the database (which can be the DBA , but can be some1 else as
well...)

I tried to avoid this solution, but now i understand that i don't have any
other choice.
encrypting the data will be useless, because i cannot SELECT by
text/range/dates....

tnx


On Wed, Jun 4, 2008 at 7:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> zferentz@gmail.com writes:
> > I'd like to use postgres to store my secret data  in a way that only
> > me (the DBA, owner of the table) can access the talbe while the root
> > (system administrator) who installed and maintains the server - will
> > not be able to see the data.
>
> If you think you can hide anything on a machine from its root admin,
> I have a bridge I'd like to sell you ...
>
> The only thing you could do along this line is to use the database as a
> dumb container for encrypted data that you decrypt only on the client
> side, using keys that are never sent to the database server.
> Unfortunately that approach loses most of the benefit of using a
> database in the first place, since you can hardly do any useful
> processing on data that you can't decrypt.
>
>                        regards, tom lane
>

view thread (7+ messages)  latest in thread

Message-ID: <96f635390806100022o11e0d033v782ff30c56391778@mail.gmail.com>
Permalink:  ../96f635390806100022o11e0d033v782ff30c56391778@mail.gmail.com/
Also on:    postgresql.org/message-id/96f635390806100022o11e0d033v782ff30c56391778@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: zferentz@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: Postgres security issue - protecting datafiles
  In-Reply-To: <96f635390806100022o11e0d033v782ff30c56391778@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox