Re: Exclude one piece of data from an export

On Fri, 6 Dec 2002 16:54:49 +0000 (UTC), "Tim Shute" <tshute_at_nisoft.com> wrote:

>Thanks for the fast reply!
>
>The problem is not in-house.
>
>What we're trying to do is prevent anyone at a client site from doing an
>export and taking it away with them. We can't control how they do their
>exports.
>
>I know we can't / don't want to stop them from seeing the data
>structures easily, but if this license key field could be automatically
>ignored (or corrupted?) by a 'normal' export, then it wouldn't be
>imported making the
>software application prompt for a license key if it was run against the
>imported data.

The only feasible way I can think of doing this is basing the key on some piece randomly acquired data and preventing the application from starting if the comparision matches (i.e. dbid, pk encryption, etc).

As far as preventing access to the table - once the database is installed on their system, they have full control over the data stored within. The only exceptions may be custom-installed (by your dev team) Trusted Oracle on a Trused os - there are way to keep their admins away from sensitive data on Trusted (military) installs, but I doubt the higher cost of these system would be justified by the fear of piracy.

As always, YMMV. Received on Mon Dec 09 2002 - 19:13:23 CST