| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | artacus(at)comcast(dot)net |
| Cc: | pgsql-general(at)postgresql(dot)org, luca ciciriello <luca(dot)ciciriello(at)email(dot)it> |
| Subject: | Re: masking the code |
| Date: | 2009-06-26 21:32:35 |
| Message-ID: | dcc563d10906261432h64b8f164xdf5fde1f25933271@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 26, 2009 at 1:37 PM, <artacus(at)comcast(dot)net> wrote:
>
> Obfuscated function source code (not wanted) Obfuscating function source
> code has minimal protective benefits because anyone with super-user access
> can find a way to view the code. At the same time, it would greatly
> complicate backups and other administrative tasks. To prevent
> non-super-users from viewing function source code, remove SELECT permission
> on pg_proc.
>
>
> I completely agree w/ HArald. Its not something we'd want to see in an open
> source product. That said, I saw yesterday that the latest version of
> EnterpriseDB has this feature. So if you want to protect your own IP, then
> you've got to purchase someone else's.
s/protect/pretend to protect/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerry Reno | 2009-06-26 21:47:59 | Re: Replication |
| Previous Message | Scott Mead | 2009-06-26 21:03:30 | Re: Terrible Write Performance of a Stored Procedure |