| From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: WIP: plpgsql source code obfuscation |
| Date: | 2008-01-28 16:04:47 |
| Message-ID: | 162867790801280804s3d447406if62fdcfb547a252a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On 28/01/2008, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
>
> Someone along the way suggested doing this as a kind of "wrapper" PL language.
> So you would have a PL language like "obfuscate:plperl" which would obfuscate
> the source code on the way in. Then when you execute a function it would
> deobfuscate the source code and then just pass it to the normal plperl.
>
you can call Deobfuscate proc from any language handler - no problem
> In such a scheme I think you would put the key in an attribute of the
> language. Either in pg_lang or some configuration location which the
> obfuscate:plperl interpreter knows where to find.
>
what is advantage?
> --
> Gregory Stark
> EnterpriseDB http://www.enterprisedb.com
> Ask me about EnterpriseDB's On-Demand Production Tuning
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-01-28 17:05:13 | Re: WIP: plpgsql source code obfuscation |
| Previous Message | Gregory Stark | 2008-01-28 15:59:30 | Re: WIP: plpgsql source code obfuscation |