pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Silvana Di Martino <silvanadimartino@tin.it>
Cc: Joe Conway <mail@joeconway.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pgcrypto and database encryption
Date: Mon, 8 Mar 2004 08:47:32 -0600
Message-ID: <20040308144732.GA7140@wolff.to> (raw)
In-Reply-To: <200403080837.37655.silvanadimartino@tin.it>
References: <200403071613.03397.silvanadimartino@tin.it>
	<404B67C6.6030106@joeconway.com>
	<200403080837.37655.silvanadimartino@tin.it>

On Mon, Mar 08, 2004 at 08:37:37 +0000,
  Silvana Di Martino <silvanadimartino@tin.it> wrote:
> Alle 18:19, domenica 7 marzo 2004, Joe Conway ha scritto:
> > Silvana Di Martino wrote:
> > > 4) What could actually solve our problem is something like the following
> > > scenario. Imagine that postmaster (or pg_ctrl) could accept a new CL
> > > parameter called "pw". This parameter would contain a sequence of
> > > comma-separated databasename/encryption-password pairs. I mean, something
> > > like this:
> > >
> > > postmaster -i -pw=postnuke:"arriba!",phpnuke:"blade runner"
> >
> > But you mentioned earlier that the DBA cannot know the passwords, so who
> > is going to type all that in?
> 
> Accordingly to law, a "authorized operator". A piece of paper transforms a 
> generic user/sysadmin into a trusted person who can perform such operations 
> (again, not our choice: law imposes it).

This sounds like the real solution to your problem. You should do what
you need to to make the system administrator an authorized user and
then use more practical security methods to secure the data.



view thread (13+ messages)  latest in thread

Message-ID: <20040308144732.GA7140@wolff.to>
Permalink:  ../20040308144732.GA7140@wolff.to/
Also on:    postgresql.org/message-id/20040308144732.GA7140@wolff.to

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: bruno@wolff.to, silvanadimartino@tin.it, mail@joeconway.com
  Subject: Re: pgcrypto and database encryption
  In-Reply-To: <20040308144732.GA7140@wolff.to>
  References: <200403071613.03397.silvanadimartino@tin.it> <404B67C6.6030106@joeconway.com> <200403080837.37655.silvanadimartino@tin.it> <20040308144732.GA7140@wolff.to>

* 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