Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 070BB9FA3A2 for ; Thu, 8 Feb 2007 10:32:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 89754-06 for ; Thu, 8 Feb 2007 10:32:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 06D949FA09C for ; Thu, 8 Feb 2007 10:32:20 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l18EUis26889; Thu, 8 Feb 2007 09:30:44 -0500 (EST) From: Bruce Momjian Message-Id: <200702081430.l18EUis26889@momjian.us> Subject: Re: database encryption In-Reply-To: <20070208115221.GA76441@winnie.fuhr.org> To: Michael Fuhr Date: Thu, 8 Feb 2007 09:30:44 -0500 (EST) CC: Olivier Boissard , Andrew Sullivan , pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/125 X-Sequence-Number: 24590 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 -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +