plperl Safe restrictions - Mailing list pgsql-hackers

From Andrew Dunstan
Subject plperl Safe restrictions
Date
Msg-id 416ECEF6.20704@dunslane.net
Whole thread Raw
Responses Re: plperl Safe restrictions
Re: plperl Safe restrictions
List pgsql-hackers
It has just been brought to my attention that we are being very 
restrictive about what we allow to be done in trusted plperl. Basically 
we allow the :default and :base_math set of operations (run perldoc 
Opcode or see http://www.perldoc.com/perl5.8.0/lib/Opcode.html for 
details of what these mean). In particular, we do not allow calls to 
perl's builtin sort, which is unpleasant, and on reviewing the list it 
seems to me we could quite reasonably allow access to pack and unpack 
also. bless and sprintf are also likely candidates for inclusion - I 
have not finished reviewing the list, and would welcome advice from perl 
gurus on this.

On the other side, I think we should exclude the :base_io set which is 
part of the :default set (we don't want trusted plperl writing to 
stdout, for example - all IO should be forbidden).

I know changing this at this stage of the dev cycle is bad, but I think 
it ought to be done. Unless there are loud squawks I will submit a patch 
RSN. It should be very low risk - one or two lines.

cheers

andrew




pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Why we still see some reports of "could not access transaction status"
Next
From: Bruce Momjian
Date:
Subject: Re: Problem with CIDR data type restrictions