| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Allan Kamau <kamauallan(at)gmail(dot)com>, akp geek <akpgeek(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Hide the code from users postgres |
| Date: | 2010-06-24 21:28:03 |
| Message-ID: | AANLkTiktz_8oF3GFkXUQdpXSEDiBPqAC7AejzlsLODxZ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jun 24, 2010 at 10:20 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> On Thu, 2010-06-24 at 22:18 +0100, Dave Page wrote:
>
>> > I have no problem with him trying to protect his hard earned work. I
>> > just think he is trying to solve the wrong problem.
>>
>> It's a real problem faced by many businesses and solved by most
>> commercial DBMSs. Of course, it's basically impossible to solve in the
>> Open Source world, as there's nowhere to hide a key or obfuscation
>> algorithm. If akp geek is able to use EnterpriseDB builds of Postgres,
>> then he may want to look at PL/Secure, which will obfuscate his
>> pl/pgsql code:
>>
>> http://www.enterprisedb.com/products/pl_secure_standard_server.do
>
> That's interesting... does it just turn it into bytecode?
No, it runs it through a few different obfuscation algorithms to make
it very difficult to decode without knowledge of them.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Singer | 2010-06-24 21:28:21 | Slony-I 2.0.4 released |
| Previous Message | Pavel Stehule | 2010-06-24 21:22:21 | Re: Hide the code from users postgres |