Re: plperl security - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plperl security
Date
Msg-id 2674.1089051608@sss.pgh.pa.us
Whole thread Raw
In response to plperl security  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: plperl security  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Currently we have this in plperl.c:
>   "require Safe;"
> I am thinking of submitting a patch to replace this with "use Safe 
> 2.09;" to enforce use of a version without the known vulnerability.

This would break both plperl and plperlu on older Perls.  Please see
if you can avoid breaking plperlu.

For that matter, does plperl.c really cope properly with a failure in
this code at all?  I sure don't see anything that looks like error
handling in plperl_init_interp().
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [Plperlng-devel] plperl security
Next
From: Simon Riggs
Date:
Subject: Recovery Features