From: Joshua D. Drake <jd@commandprompt.com>
To: Roberts, Jon <Jon.Roberts@asurion.com>
Cc: 'Jonah H. Harris' <jonah.harris@gmail.com>
Cc: Bill Moran <wmoran@collaborativefusion.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: viewing source code
Date: Mon, 17 Dec 2007 08:13:43 -0800
Message-ID: <4766A037.7040203@commandprompt.com> (raw)
In-Reply-To: <1A6E6D554222284AB25ABE3229A92762112A00@nrtexcus702.int.asurion.com>
References: <1A6E6D554222284AB25ABE3229A92762112A00@nrtexcus702.int.asurion.com>
Roberts, Jon 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.
Actually I suggested using a obfuscation module.
>
> If it isn't a feature today, what table has the source code in it? Maybe I
> can revoke that.
If your pl is perl or plpgsql it will be in the prosrc (pro_src?) column
in pg_proc.
Joshua D. Drake
>
>
> Jon
>> -----Original Message-----
>> From: Jonah H. Harris [mailto:jonah.harris@gmail.com]
>> Sent: Friday, December 14, 2007 3:04 PM
>> To: Bill Moran
>> Cc: Joshua D. Drake; Roberts, Jon; pgsql-performance@postgresql.org
>> Subject: Re: [PERFORM] viewing source code
>>
>> On Dec 14, 2007 2:03 PM, Bill Moran <wmoran@collaborativefusion.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.harris@enterprisedb.com
>> Edison, NJ 08837 | http://www.enterprisedb.com/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jd@commandprompt.com, Jon.Roberts@asurion.com, jonah.harris@gmail.com, wmoran@collaborativefusion.com
Subject: Re: viewing source code
In-Reply-To: <4766A037.7040203@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox