Re: Specification for Trusted PLs?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>
Cc: Jan Wieck <JanWieck(at)yahoo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joshua Tolley <eggyknap(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Specification for Trusted PLs?
Date: 2010-05-23 03:09:42
Message-ID: AANLkTikFvcC7g9wSplJaU3RbWGf467VRxC2Nx59sNhNe@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 22, 2010 at 4:53 PM, Cédric Villemain
<cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
> 2010/5/21 Jan Wieck <JanWieck(at)yahoo(dot)com>:
>> The original idea was that a trusted language does not allow an unprivileged
>> user to gain access to any object or data, he does not have access to
>> without that language.
>>
>> This does not include data transformation functionality, like string
>> processing or the like. As long as the user had legitimate access to the
>> input datum, then every derived form thereof is OK.
>
> I find the current doc enough, add this prose from Jan as a comment
> might help people perhaps.

Yeah, Jan's description is very clear and to the point.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2010-05-23 03:20:50 [PATCH] Move 'long long' check to c.h
Previous Message Robert Haas 2010-05-23 03:08:02 Re: "unexpected" query behaviour after i change parser code