From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Marius Pitigoi <marius(dot)pitigoi(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How psql source code can be protected? |
Date: | 2010-01-07 13:18:18 |
Message-ID: | b42b73151001070518m356ed646gbdbe5b0bf8ca4f1f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jan 6, 2010 at 11:09 AM, Marius Pitigoi
<marius(dot)pitigoi(at)gmail(dot)com> wrote:
> Hello,
>
> Is there a way to protect psql source code? For example oracle has wrap
> utility.
> I want to deploy my DB on a hosting company server. But they can see my
> functions code (they have root privileges) and this is what I want to avoid.
It's impossible to do this if the company has access to the database
superuser account. If they have root access on the box there is no
real effective way from keeping them from using that account (your
main line of defense is pg_hba.conf which they can simply adjust).
If you limit them to a restricted account you can prevent casual
browsing of your procedure code by revoking select access from pg_proc
from that account and 'public'.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2010-01-07 13:23:49 | Re: Rows missing from table despite FK constraint |
Previous Message | Alban Hertroys | 2010-01-07 10:49:07 | Re: interesting check constraint behavior |