X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7F235D91A5 for ; Fri, 23 Sep 2005 12:23:49 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98458-01 for ; Fri, 23 Sep 2005 15:23:46 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 4F210D917C for ; Fri, 23 Sep 2005 12:23:45 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 23 Sep 2005 10:23:44 -0500 Subject: Re: Encrypted Disks From: Scott Marlowe To: Peter Darley Cc: Pgsql-Admin In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1127489023.30825.82.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 23 Sep 2005 10:23:44 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200509/271 X-Sequence-Number: 19008 On Thu, 2005-09-22 at 17:18, Peter Darley wrote: > Folks, > > A client is asking us about data security, and keeping data encrypted on > disk. I recall there was some discussion about this before, including > things like for it to be secure an operator would need to put in a key when > the disk is mounted, that once it is mounted anyone with permissions to the > disk can read it, etc. > > Given these drawbacks, I'm wondering if anyone has used an encrypted fs for > PostgreSQL and if so, what they found in terms of speed. Would this be a > big hit, or would it be pretty low impact? Also, does it cause any > potential problems with recovery from a crash, etc? You and your client need to back up and figure out which scenario you're trying to protect against. Encrypting the drive (with an external key) ensures that if someone steals the disks, or gets hold of the raw db files that they can't get the data out. However, if they hack into the machine that is accessing the database, encrypting the drives doesn't nothing for you. So, which scenario are they trying to protect against? Once you know the answer to that question, then you can look at different ways of encrypting the data you are storing.