| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| 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:20:58 |
| Message-ID: | 1277414458.19443.53.camel@jd-desktop.unknown.charter.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
Joshua D. Drake
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-06-24 21:22:21 | Re: Hide the code from users postgres |
| Previous Message | Pavel Stehule | 2010-06-24 21:20:55 | Re: Hide the code from users postgres |