| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: WIP: plpgsql source code obfuscation |
| Date: | 2008-01-29 14:33:30 |
| Message-ID: | 479F393A.5090504@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Peter Eisentraut wrote:
> Am Montag, 28. Januar 2008 schrieb Pavel Stehule:
>
>> 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).
>>
>
> Have you thought about a solution that applies the regular access privileges
> to pg_proc in order to hide some content from less privileged users?
>
>
This question is a good one, especially since we have waiting in the
wings the work my SOC student did a few months ago on column level
privileges.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-01-29 14:52:46 | Re: WIP: plpgsql source code obfuscation |
| Previous Message | Peter Eisentraut | 2008-01-29 14:21:42 | Re: WIP: plpgsql source code obfuscation |