X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D7D69D1B562 for ; Mon, 8 Mar 2004 14:44:47 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 06004-09 for ; Mon, 8 Mar 2004 10:44:48 -0400 (AST) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 08039D1B51F for ; Mon, 8 Mar 2004 10:44:44 -0400 (AST) Received: (qmail 5530 invoked by uid 500); 8 Mar 2004 14:47:32 -0000 Date: Mon, 8 Mar 2004 08:47:32 -0600 From: Bruno Wolff III To: Silvana Di Martino Cc: Joe Conway , pgsql-admin@postgresql.org Subject: Re: pgcrypto and database encryption Message-ID: <20040308144732.GA7140@wolff.to> Mail-Followup-To: Silvana Di Martino , Joe Conway , pgsql-admin@postgresql.org References: <200403071613.03397.silvanadimartino@tin.it> <404B67C6.6030106@joeconway.com> <200403080837.37655.silvanadimartino@tin.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403080837.37655.silvanadimartino@tin.it> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/124 X-Sequence-Number: 12693 On Mon, Mar 08, 2004 at 08:37:37 +0000, Silvana Di Martino 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.