| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
| Cc: | artacus(at)comcast(dot)net, pgsql-general(at)postgresql(dot)org, luca ciciriello <luca(dot)ciciriello(at)email(dot)it> |
| Subject: | Re: masking the code |
| Date: | 2009-06-29 13:35:09 |
| Message-ID: | 36e682920906290635l80eaf2au14f37e6dff7f0298@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 29, 2009 at 9:31 AM, Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>wrote:
>
> It is important to note (as many people have already pointed out) that
> both EnterpriseDB and Oracle's wrap functionality is declared as a 100%
> guarantee that nobody can read your code. As with many different types of
> security (i.e. the 3 foot high fence) this is really just a deterrent to
> most people who either aren't capable of reverse engineering or are just not
> interested in the first place.
>
s/is declared/is NOT declared/g
:)
--
Jonah H. Harris, Senior DBA
myYearbook.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Mead | 2009-06-29 13:37:48 | Re: masking the code |
| Previous Message | A. Kretschmer | 2009-06-29 13:34:18 | Re: Am I in intransaction or in autocommit mode? |