From: Bruno Wolff III <bruno@wolff.to>
To: Daniel Struck <struck.d@retrovirology.lu>
Cc: Mitch Pirtle <mitchy@spacemonkeylabs.com>
Cc: pgsql-php@postgresql.org
Subject: Re: [ADMIN] Secure DB Systems - How to
Date: Tue, 27 Jul 2004 14:49:05 -0500
Message-ID: <20040727194905.GA20499@wolff.to> (raw)
In-Reply-To: <20040727134133.676ab9cf@localhost>
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>
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.
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bruno@wolff.to, struck.d@retrovirology.lu, mitchy@spacemonkeylabs.com, pgsql-php@postgresql.org
Subject: Re: [ADMIN] Secure DB Systems - How to
In-Reply-To: <20040727194905.GA20499@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