Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] plperl Safe restrictions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] plperl Safe restrictions
Date: 2004-11-16 22:06:15
Message-ID: 3097.1100642775@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> It has just been brought to my attention that we are being very 
> restrictive about what we allow to be done in trusted plperl. 
> ...
> OK, based on this and some further thought, I have prepared the attached 
> patch which does the right thing, I think, both in terms of what we 
> allow and what we don't.

Applied, with changes to allow srand and disallow sprintf, as per
subsequent discussion.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: John HansenDate: 2004-11-16 22:20:23
Subject: Re: [PATCHES] plperl Safe restrictions
Previous:From: Tom LaneDate: 2004-11-16 21:37:20
Subject: Re: GiST: PickSplit and multi-attr indexes

pgsql-patches by date

Next:From: John HansenDate: 2004-11-16 22:20:23
Subject: Re: [PATCHES] plperl Safe restrictions
Previous:From: Joshua D. DrakeDate: 2004-11-16 21:26:17
Subject: Re: Win32 signals & sockets

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group