Re: Specification for Trusted PLs? - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Specification for Trusted PLs?
Date
Msg-id AANLkTinyFfv21KMHcuD2sLRdHRoJw4nUX8E6x5bc9x9q@mail.gmail.com
Whole thread Raw
In response to Re: Specification for Trusted PLs?  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Specification for Trusted PLs?
List pgsql-hackers
> That's about it- a language is TRUSTED if there's no way for a user to
> be able to write a function which will give them access to things
> they're not supposed to have.  Practically, this includes things like
> any kind of direct I/O (files, network, etc).

The fact that plpythonu used to be plpython back in 7.3 serves to
illustrate that the distinction is not all that well defined. I guess
that someone made an executive decision that the python restricted
execution environment wasn't restricted enough.

Regards,
Peter Geoghegan


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Specification for Trusted PLs?
Next
From: Tom Lane
Date:
Subject: Re: Specification for Trusted PLs?