Skip site navigation (1) Skip section navigation (2)

Re: WIP: plpgsql source code obfuscation

From: "Dave Page" <dpage(at)postgresql(dot)org>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: WIP: plpgsql source code obfuscation
Date: 2008-01-28 14:04:02
Message-ID: 937d27e10801280604r48dfd504i484c0db879b692c7@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-patches
On Jan 28, 2008 12:51 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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

In response to

Responses

pgsql-patches by date

Next:From: Florian G. PflugDate: 2008-01-28 14:23:19
Subject: Re: [8.4] Updated WITH clause patch (non-recursive)
Previous:From: Jonah H. HarrisDate: 2008-01-28 13:51:30
Subject: Re: [PATCHES] Including Snapshot Info with Indexes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group