Date: Tue, 27 Jul 2004 14:49:05 -0500
From: Bruno Wolff III <bruno@wolff.to>
To: Daniel Struck <struck.d@retrovirology.lu>
Cc: Mitch Pirtle <mitchy@spacemonkeylabs.com>,
	pgsql-php@postgresql.org
Subject: Re: [ADMIN] Secure DB Systems - How to
Message-ID: <20040727194905.GA20499@wolff.to>
Mail-Followup-To: Daniel Struck <struck.d@retrovirology.lu>,
	Mitch Pirtle <mitchy@spacemonkeylabs.com>, pgsql-php@postgresql.org
References: <ccjra4$pgl$1@sea.gmane.org> <20040709152722.GA20935@wolff.to>
	<20040713113557.31e9d6dc@localhost>
	<20040713123817.GB3710@wolff.to>
	<20040713151838.0004cb8e@localhost>
	<40F3EC4A.1060101@spacemonkeylabs.com>
	<20040727134133.676ab9cf@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040727134133.676ab9cf@localhost>
User-Agent: Mutt/1.5.6i

On Tue, Jul 27, 2004 at 13:41:33 +0200,
  Daniel Struck <struck.d@retrovirology.lu> wrote:
> > Exactly.  That is the only way to ensure that the data is never 
> > decrypted within the database or database server.
> 
> But then one will also lose the ability to make sql-queries with the encrypted columns . Something I wouldn't want to miss, or else it doesn't make sense to store this data in a database if one can't work with it.

That depends on the kind of queries. Searching for exact matches should
work fine. Some other things can be done in special cases.

If you are interested in this topic you may want to pick up a copy of
Translucent Databases.