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 DE879D1BB91 for ; Sun, 7 Mar 2004 22:16: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 17420-10 for ; Sun, 7 Mar 2004 18:16:47 -0400 (AST) Received: from bayswater1.ymogen.net (unknown [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id D9C3FD1B530 for ; Sun, 7 Mar 2004 18:16:44 -0400 (AST) Received: by bayswater1.ymogen.net (Postfix, from userid 99) id D91969AD1C; Sun, 7 Mar 2004 22:16:44 +0000 (GMT) Received: from 82.68.132.233 (SquirrelMail authenticated user matt@ymogen.net) by webmail.ymogen.com with HTTP; Sun, 7 Mar 2004 22:16:44 -0000 (GMT) Message-ID: <3195.82.68.132.233.1078697804.squirrel@webmail.ymogen.com> In-Reply-To: <404B67C6.6030106@joeconway.com> References: <200403071613.03397.silvanadimartino@tin.it> <404B67C6.6030106@joeconway.com> Date: Sun, 7 Mar 2004 22:16:44 -0000 (GMT) Subject: Re: pgcrypto and database encryption From: matt@ymogen.net To: "Joe Conway" Cc: "Silvana Di Martino" , pgsql-admin@postgresql.org User-Agent: SquirrelMail/1.4.2-0.1.7.x MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/112 X-Sequence-Number: 12681 > Does the law require protection from a determined DBA, or just casual > viewing by the DBA? *If* it's the latter, you could do something like > this: The EU directive (and therefore the laws of indiviual countries) requires that if someone gets access to your *DATABASE* they cannot get personal details of individuals out of it. That is all. It is intended to protect people against the kind of idiotic organisations that put their customer lists in an Excel sheet on their extranet without a password. This thread has covered many interesting and diverting issues, but the fundamental issue of legal compliance is more than satisfied by: 1) Encrypting 'personal information' stored in a DB 2) Keeping the keys on a different server than the DB 3) Making reasonable efforts [1] to keep those keys secrets M [1] As far as I can tell from discussions with the Data Protection Registrar, you do not have to protect them against someone rooting the app server (since that is essentially impossible without silly investments in specialised hardware or other excessive costs).