| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Specification for Trusted PLs? |
| Date: | 2010-05-21 16:12:42 |
| Message-ID: | 4BF6B0FA.1090602@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/21/2010 11:57 AM, Magnus Hagander wrote:
> On Fri, May 21, 2010 at 11:55 AM, Josh Berkus<josh(at)agliodbs(dot)com> wrote:
>> So, here's a working definition:
>>
>> 1) cannot directly read or write files on the server.
>> 2) cannot bind network ports
>
> To make that more covering, don't yu really need something like
> "cannot communicate with outside processes"?
So, no interprocess communication except through the SPI interface? How
do module GUCs and things like %_SHARED fit into this?
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-05-21 16:22:20 | Re: Specification for Trusted PLs? |
| Previous Message | Magnus Hagander | 2010-05-21 15:57:33 | Re: Specification for Trusted PLs? |