Re: viewing source code

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: viewing source code
Date: 2007-12-17 14:13:52
Message-ID: b42b73150712170613y1bf9b208vdb3e48532ad16b66@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Dec 17, 2007 8:11 AM, Roberts, Jon <Jon(dot)Roberts(at)asurion(dot)com> wrote:
> Alvaro Herrera pointed out that pg_read_file requires superuser access which
> these users won't have so revoking access to the function code should be
> possible.
>
> Joshua D. Drake suggested revoking pg_proc but that isn't the source code,
> it just has the definition of the functions.
>
> If it isn't a feature today, what table has the source code in it? Maybe I
> can revoke that.

the table is pg_proc. you have to revoke select rights from public
and the user of interest. be aware this will make it very difficult
for that user to do certain things in psql and (especially) pgadmin.
it works.

a better solution to this problem is to make a language wrapper for
pl/pgsql that encrypts the source on disk. afaik, no one is working on
th is. it would secure the code from remote users but not necessarily
from people logged in to the server. the pg_proc hack works ok
though.

merlin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2007-12-17 15:45:43 Re: VACUUM FREEZE output more than double input
Previous Message Roberts, Jon 2007-12-17 13:11:36 Re: viewing source code