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 99786D1D17E for ; Mon, 8 Mar 2004 14:07:24 +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 02772-04 for ; Mon, 8 Mar 2004 10:07:25 -0400 (AST) Received: from fep04-mail.bloor.is.net.cable.rogers.com (fep04-mail.bloor.is.net.cable.rogers.com [66.185.86.74]) by svr1.postgresql.org (Postfix) with ESMTP id 512D9D1CCC5 for ; Mon, 8 Mar 2004 10:07:21 -0400 (AST) Received: from phlogiston.dydns.org ([65.49.121.67]) by fep04-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20040308140657.DCNB3598.fep04-mail.bloor.is.net.cable.rogers.com@phlogiston.dydns.org> for ; Mon, 8 Mar 2004 09:06:57 -0500 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 523CF3F40; Mon, 8 Mar 2004 09:07:24 -0500 (EST) Date: Mon, 8 Mar 2004 09:07:24 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: HIPAA Message-ID: <20040308140724.GB24861@phlogiston.dyndns.org> Mail-Followup-To: pgsql-admin@postgresql.org References: <200403081024.06324.silvanadimartino@tin.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200403081024.06324.silvanadimartino@tin.it> User-Agent: Mutt/1.5.4i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep04-mail.bloor.is.net.cable.rogers.com from [65.49.121.67] using ID at Mon, 8 Mar 2004 09:06:57 -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/123 X-Sequence-Number: 12692 On Mon, Mar 08, 2004 at 12:07:23PM +0000, Silvana Di Martino wrote: > This seems to give to this "db encryption" issue the status of "global > relevance" that would deserve a more systematic approach. I mean: no > homegrown solutions - rather have the community to develop a specific, > standard extension of PostgreSQL and put it into the distro. Just to throw another wrench into the works, you might want to think about some of the observations on what data you _really_ need that are in Peter Wayner's _Translucent Databases_ (Flyzone Press, 2002. ISBN 0-9675844-1-8). Many of the techniques are not particularly novel, but the discussion in the beginning about deciding just which data you _really_ need is, I think, very helpful. There's a tendency to collect data just because one can, and the new data protection laws are an attempt to find a techno fix to the problem. (I still like it that someone is spending some time on improving the crypto stuff, though.) A -- Andrew Sullivan | ajs@crankycanuck.ca The fact that technology doesn't work is no bar to success in the marketplace. --Philip Greenspun