Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 026259FB388 for ; Fri, 9 Feb 2007 07:38:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 38184-02-4 for ; Fri, 9 Feb 2007 07:37:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mx.imatech.net (mx.imatech.net [81.255.215.253]) by postgresql.org (Postfix) with ESMTP id 4B0599FA5D8 for ; Fri, 9 Feb 2007 04:03:04 -0400 (AST) X-AuthUser: olivier.boissard@cerene.fr Received: from [200.200.200.34] ([195.6.193.141]:36709) by mx.imatech.net with [XMail 1.23 ESMTP Server] id for from ; Fri, 9 Feb 2007 09:03:14 +0100 Message-ID: <45CC2AC8.5020005@cerene.fr> Date: Fri, 09 Feb 2007 09:03:20 +0100 From: Olivier Boissard Organization: cerene services User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Bruce Momjian CC: Michael Fuhr , Andrew Sullivan , pgsql-admin@postgresql.org Subject: Re: database encryption References: <200702081430.l18EUis26889@momjian.us> In-Reply-To: <200702081430.l18EUis26889@momjian.us> Content-Type: multipart/mixed; boundary="------------000205080309070106090002" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/130 X-Sequence-Number: 24595 This is a multi-part message in MIME format. --------------000205080309070106090002 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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 --------------000205080309070106090002 Content-Type: text/x-vcard; charset=utf-8; name="olivier.boissard.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="olivier.boissard.vcf" 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 --------------000205080309070106090002--