Re: [Plperlng-devel] Re: plperl security - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: [Plperlng-devel] Re: plperl security
Date
Msg-id Pine.LNX.4.44.0407092008320.1262-100000@hosting.commandprompt.com
Whole thread Raw
In response to Re: plperl security  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hello,

I know there is a patch coming Monday with a great deal of bug fixes.

J


On Fri, 9 Jul 2004, Tom Lane wrote:

> Andrew Dunstan <andrew@dunslane.net> writes:
> > OK, I have a setup that instead of refusing to load trusted functions if 
> > the Safe version is not up to date, forces them to error out by calling 
> > elog(ERROR...), thus:
> 
> > andrew=# select tval();
> > ERROR:  trusted perl functions disabled - please upgrade perl Safe 
> > module to at least 2.09
> 
> > This seems like perfectly reasonable recovery to me. Thoughts?
> 
> Works for me --- and it doesn't leak memory across repeated failures,
> right?
> 
> Patch please?
> 
>             regards, tom lane
> _______________________________________________
> Plperlng-devel mailing list
> Plperlng-devel@pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/plperlng-devel
> 

-- 
Co-Founder
Command Prompt, Inc.
The wheel's spinning but the hamster's dead



pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: [PATCHES] Fixes for pg_dump and ownership/acl problems
Next
From: Tom Lane
Date:
Subject: Re: SAN, clustering, MPI, Backplane Re: Postgresql on SAN