X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 5F3089DC81B for ; Thu, 15 Dec 2005 18:42:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 92390-01 for ; Thu, 15 Dec 2005 18:42:08 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 59F989DC835 for ; Thu, 15 Dec 2005 18:42:04 -0400 (AST) 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; 15 Dec 2005 16:42:05 -0600 Subject: Re: Protecting application table structures and data From: Scott Marlowe To: David Pratt Cc: "Jim C. Nasby" , pgsql-admin@postgresql.org In-Reply-To: <43A1ECEC.8050807@eastlink.ca> References: <43A1D9BB.2030601@eastlink.ca> <20051215220056.GH40699@pervasive.com> <43A1ECEC.8050807@eastlink.ca> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1134686525.8351.1.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 15 Dec 2005 16:42:05 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200512/160 X-Sequence-Number: 19880 On Thu, 2005-12-15 at 16:23, David Pratt wrote: > Hi Jim. Many thanks for your reply. I guess this is not so great news. I > am sort of at a loss as to what direction to take. I need a db > connection on a couple of threads minimum in my app but also need to > ensure that the information is secure. Let's face facts. The second you hand the user a CDROM with your application and encoded data on it, and the application has a way to access it, it's only a matter of time before the user, by hacking the application, can get access to it. There is one, and only one, real solution. Host the data yourself and require the user to connect remotely to you. For instances of attempts to make things secure on remote systems, see the recent Sony - F4I - root kit debacle.