pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Olivier Boissard <olivier.boissard@cerene.fr>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Michael Fuhr <mike@fuhr.org>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: database encryption
Date: Fri, 9 Feb 2007 10:28:27 -0600
Message-ID: <20070209162827.GA17098@wolff.to> (raw)
In-Reply-To: <45CC2AC8.5020005@cerene.fr>
References: <200702081430.l18EUis26889@momjian.us>
	<45CC2AC8.5020005@cerene.fr>

On Fri, Feb 09, 2007 at 09:03:20 +0100,
  Olivier Boissard <olivier.boissard@cerene.fr> wrote:
> Thanks for responses.
> I expose the context of my question :
> 
> I need to install a server for a specific web application written in PHP.
> This one works by making queries to a postgresql database. The database 
> contains confidential data.

Who are you trying to keep this data from? Does this include the client?
Who needs to see the decrypted data? Does the database need to in order
to efficiently do queries? Does the webserver/php server need to or does
it produce output that the end user can download and decrypt on their end?

> For several reasons the server will be installed inside the Local 
> network of our client. I will not be able to supervise and control it.

Again, is your client being treated as an opponent? Are you worried about
other threats such as stolen servers or back up tapes?

> As it's a fussy situation I am thinking about encryption.
> I was thinking about PHP encryption solution (Zend or Ioncube) for the 
> web application protection.
> But sensitive data must be protected too.

Again, from who?

> Pgcrypto seemed to be the encryption solution but I am not sure it's a 
> good idea because all keys will be located on server ( if I have well 
> understood) and the documention explain that the data will appear on 
> "clear text" for a short period.

Whether or not that is a problem depends on what kind of attacks you are
trying to protect against. If you are trying to protect against the case
where the db server gets owned, having the keys on the server will make them
available to the attacker.



view thread (10+ messages)

Message-ID: <20070209162827.GA17098@wolff.to>
Permalink:  ../20070209162827.GA17098@wolff.to/
Also on:    postgresql.org/message-id/20070209162827.GA17098@wolff.to

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: bruno@wolff.to, olivier.boissard@cerene.fr, bruce@momjian.us, mike@fuhr.org, ajs@crankycanuck.ca
  Subject: Re: database encryption
  In-Reply-To: <20070209162827.GA17098@wolff.to>
  References: <200702081430.l18EUis26889@momjian.us> <45CC2AC8.5020005@cerene.fr> <20070209162827.GA17098@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