Re: WIP: plpgsql source code obfuscation - Mailing list pgsql-patches

From Pavel Stehule
Subject Re: WIP: plpgsql source code obfuscation
Date
Msg-id 162867790801280804s3d447406if62fdcfb547a252a@mail.gmail.com
Whole thread Raw
In response to Re: WIP: plpgsql source code obfuscation  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: WIP: plpgsql source code obfuscation
List pgsql-patches
On 28/01/2008, Gregory Stark <stark@enterprisedb.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
>

pgsql-patches by date:

Previous
From: Gregory Stark
Date:
Subject: Re: WIP: plpgsql source code obfuscation
Next
From: Gregory Stark
Date:
Subject: Re: WIP: plpgsql source code obfuscation