| From: | Scott Mead <scott(dot)mead(at)enterprisedb(dot)com> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(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:37:48 |
| Message-ID: | d3ab2ec80906290637n461aa4f3r2e6634543daa237c@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 29, 2009 at 9:35 AM, Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com>wrote:
> 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
Yes! Jeez, this cold is getting to me. Thanks Jonah... :
It is important to note (as many people have already pointed out) that
both EnterpriseDB and Oracle's wrap functionality is NOT declared as a 100%
guarantee that nobody can read your code.
--Scott
>
>
> :)
>
> --
> Jonah H. Harris, Senior DBA
> myYearbook.com
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Mead | 2009-06-29 13:38:26 | Re: masking the code |
| Previous Message | Jonah H. Harris | 2009-06-29 13:35:09 | Re: masking the code |