X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CDDEBD1D5A6 for ; Fri, 5 Mar 2004 11:17:57 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 73363-02 for ; Fri, 5 Mar 2004 07:17:56 -0400 (AST) Received: from bayswater1.ymogen.net (unknown [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id E627BD1CA50 for ; Fri, 5 Mar 2004 07:17:52 -0400 (AST) Received: from solent (82-68-95-1.dsl.in-addr.zen.co.uk [82.68.95.1]) by bayswater1.ymogen.net (Postfix) with ESMTP id CF5F59AC9D; Fri, 5 Mar 2004 11:17:52 +0000 (GMT) From: "Matt Clark" To: "Dave Ewart" , Subject: Re: Database Encryption (now required by law in Italy) Date: Fri, 5 Mar 2004 11:17:52 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <20040305092041.GB13042@nemesis.ox.icnet.uk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/31 X-Sequence-Number: 12601 > What's wrong with using a LoopAES filesystem? It protects against > someone walking off with the server, or at least the hard disk, and > being able to see the data. Yes, but only if the password has to entered manually [1] at boot time. And it gives zero protection against someone who gains root access to the server. So you _also_ have to encrypt the sensitive data before giving it to the DB, using a key that is not stored on the DB server. Of course that means your app servers have to have _those_ passwords/ keys entered manually at boot time, or else someone who roots them can read your sensitive data quite trivially. And to do any better than that you need one of those very snazzy cards from nCipher or whoever, that allow you to process encrypted data in a hardware sandbox so even your application doesn't see it, or at least only allow signed code to manipulate the data. Matt [1] There are ways of avoiding having to enter the info manually, but they're very tricky to implement securely.