From: Scott Marlowe <smarlowe@g2switchworks.com>
To: David Pratt <fairwinds@eastlink.ca>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Protecting application table structures and data
Date: Thu, 15 Dec 2005 16:42:05 -0600
Message-ID: <1134686525.8351.1.camel@state.g2switchworks.com> (raw)
In-Reply-To: <43A1ECEC.8050807@eastlink.ca>
References: <43A1D9BB.2030601@eastlink.ca>
<20051215220056.GH40699@pervasive.com>
<43A1ECEC.8050807@eastlink.ca>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, fairwinds@eastlink.ca, jnasby@pervasive.com
Subject: Re: Protecting application table structures and data
In-Reply-To: <1134686525.8351.1.camel@state.g2switchworks.com>
References: <43A1D9BB.2030601@eastlink.ca> <20051215220056.GH40699@pervasive.com> <43A1ECEC.8050807@eastlink.ca> <1134686525.8351.1.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox