From: Greg Stark <gsstark@mit.edu>
To: Bruno Wolff III <bruno@wolff.to>
Cc: 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: 28 Jul 2004 16:16:10 -0400
Message-ID: <87brhzsx9x.fsf@stark.xeocode.com> (raw)
In-Reply-To: <20040727194905.GA20499@wolff.to>
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>
<20040727194905.GA20499@wolff.to>
Bruno Wolff III <bruno@wolff.to> writes:
> That depends on the kind of queries. Searching for exact matches should work
> fine. Some other things can be done in special cases.
If searching for exact matches works then you're using a naive encryption
system. The problem is that it also means your database is vulnerable to
dictionary attacks. Good encryption systems will include random padding to
ensure that you can't attack it by merely guessing many possible plaintexts
and verifying to see if any match.
--
greg
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: gsstark@mit.edu, 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: <87brhzsx9x.fsf@stark.xeocode.com>
* 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