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

From Dave Page
Subject Re: WIP: plpgsql source code obfuscation
Date
Msg-id 937d27e10801280604r48dfd504i484c0db879b692c7@mail.gmail.com
Whole thread Raw
In response to WIP: plpgsql source code obfuscation  ("Pavel Stehule" <pavel.stehule@gmail.com>)
Responses Re: WIP: plpgsql source code obfuscation
List pgsql-patches
On Jan 28, 2008 12:51 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> Hello
>
> this patch define new function flag - OBFUSCATE. With this flag
> encrypted source code is stored to probin column. Password is stored
> in GUC_SUPERUSER_ONLY item - it is similar security like SQL Server
> does (where privileged users can access system tables with source code
> or can use debugger).
>
> ToDo: Dump

Without making any comment of whether or not we should actually do
this, a flag in pg_proc to indicate that the function is obfuscated
would be handy for apps like pgAdmin, rather than assuming a - in
prosrc has that meaning (which may be valid for some interpreters).

/D

pgsql-patches by date:

Previous
From: "Jonah H. Harris"
Date:
Subject: Re: [HACKERS] Including Snapshot Info with Indexes
Next
From: "Florian G. Pflug"
Date:
Subject: Re: [8.4] Updated WITH clause patch (non-recursive)