From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
---|---|
To: | "'Jonah H(dot) Harris'" <jonah(dot)harris(at)gmail(dot)com>, Bill Moran <wmoran(at)collaborativefusion(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: viewing source code |
Date: | 2007-12-17 13:11:36 |
Message-ID: | 1A6E6D554222284AB25ABE3229A92762112A00@nrtexcus702.int.asurion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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.
Jon
> -----Original Message-----
> From: Jonah H. Harris [mailto:jonah(dot)harris(at)gmail(dot)com]
> Sent: Friday, December 14, 2007 3:04 PM
> To: Bill Moran
> Cc: Joshua D. Drake; Roberts, Jon; pgsql-performance(at)postgresql(dot)org
> Subject: Re: [PERFORM] viewing source code
>
> On Dec 14, 2007 2:03 PM, Bill Moran <wmoran(at)collaborativefusion(dot)com>
> wrote:
> > I disagree here. If they're connecting remotely to PG, they have no
> > direct access to the disk.
>
> pg_read_file?
>
> --
> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
> EnterpriseDB Corporation | fax: 732.331.1301
> 499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
> Edison, NJ 08837 | http://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2007-12-17 14:13:52 | Re: viewing source code |
Previous Message | Bruce Momjian | 2007-12-17 08:52:16 | Re: libgcc double-free, backend won't die |