From: Bruno Wolff III <bruno@wolff.to>
To: Daniel Struck <struck.d@retrovirology.lu>
Cc: Sarah Tanembaum <sarahtanembaum@yahoo.com>
Cc: pgsql-php@postgresql.org
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers-win32@postgresql.org
Cc: pgadmin-support@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [PHP] Secure DB Systems - How to
Date: Tue, 13 Jul 2004 07:38:17 -0500
Message-ID: <20040713123817.GB3710@wolff.to> (raw)
In-Reply-To: <20040713113557.31e9d6dc@localhost>
References: <ccjra4$pgl$1@sea.gmane.org>
<20040709152722.GA20935@wolff.to>
<20040713113557.31e9d6dc@localhost>
On Tue, Jul 13, 2004 at 11:35:57 +0200,
Daniel Struck <struck.d@retrovirology.lu> wrote:
> > Keeping the system administrator from seeing the data while making it
> > searchable is difficult. To do this you need to encrypt the data on
> > the client side using a key the client has (and this key has to be
> > protected from loss) and the only searches you can do are equality
> > searches using a hash or encrypted value.
>
> You can also perform regex searches.
If you decrypt the data on the database, the sysadmin can see it.
If you are willing to take that chance (e.g. if you primary concern is
some third party getting a snapshot of the DB), then you can do lots of
things.
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, sarahtanembaum@yahoo.com, pgsql-php@postgresql.org, pgsql-admin@postgresql.org, pgsql-hackers-win32@postgresql.org, pgadmin-support@postgresql.org
Subject: Re: [PHP] Secure DB Systems - How to
In-Reply-To: <20040713123817.GB3710@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