pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Olivier Boissard <olivier.boissard@cerene.fr>
To: 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, 09 Feb 2007 09:03:20 +0100
Message-ID: <45CC2AC8.5020005@cerene.fr> (raw)
In-Reply-To: <200702081430.l18EUis26889@momjian.us>
References: <200702081430.l18EUis26889@momjian.us>

Bruce Momjian a écrit :
> Michael Fuhr wrote:
>   
>> On Thu, Feb 08, 2007 at 09:13:48AM +0100, Olivier Boissard wrote:
>>     
>>> I was thinking about a system in which only the php programs will be 
>>> able to manage stored informations. In case of  theft or unexpected 
>>> access to servers nobody could be able to retrieve the stored data 
>>> without the authorized key.
>>>       
>> What about theft or compromise of the server running the PHP code?
>> In general it's a good idea to encrypt and decrypt as close to where
>> the cleartext is needed to limit exposure, but you should also
>> consider the vulnerability of the system that holds the key.  For
>> some applications it might make sense to use public-key encryption
>> with the exposed (e.g., Internet-facing) server having only the
>> public (encryption) key and a more protected backend server having
>> the corresponding private (decryption) key.
>>
>> Without knowing the requirements and the threat model it's impossible
>> to suggest a suitable solution.  Can you be more specific about what
>> you're trying to do?
>>     
>
> We do have an encryption section in our documentation:
>
> 	http://www.postgresql.org/docs/8.2/static/encryption-options.html
>
>
>   
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.
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.
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.
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.

Olivier

Attachments:

olivier.boissard.vcf (text/x-vcard, 239B) download begin:vcard fn:Olivier Boissard n:Boissard;Olivier org:Cerene Services adr:;;3 rue Archimede;La Chapelle Saint Luc;;10000;France email;internet:olivier.boissard@cerene.fr tel;work:03.25.74.11.78 tel;fax:03.25.78.39.67 version:2.1 end:vcard

view thread (10+ messages)  latest in thread

Message-ID: <45CC2AC8.5020005@cerene.fr>
Permalink:  ../45CC2AC8.5020005@cerene.fr/
Also on:    postgresql.org/message-id/45CC2AC8.5020005@cerene.fr

 · 

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

* 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