Re: plperl vs. plperlu - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: plperl vs. plperlu
Date
Msg-id 40EFE9A3.1070508@dunslane.net
Whole thread Raw
In response to plperl vs. plperlu  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: plperl vs. plperlu
List pgsql-hackers
If trusted, the function is located inside a perl Safe container, a 
mechanism designed for just this purpose. Try doing something forbidden 
inside a trusted function (like opening a file) and you will see the error.

cheers

andrew

Jan Wieck wrote:

> while playing with the OSCON CD's, I noticed that the current version 
> of plperl installs the same function handler for both, plperl and 
> plperlu. I was wondering how it implements the important security 
> difference or, in case it is not handled and both are in fact the 
> same, who ignored this IMHO important difference in the naming 
> convention of procedural languages.
>
>
> Jan
>


pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: plperl vs. plperlu
Next
From: Jan Wieck
Date:
Subject: Re: Recovery Features