Re: PlPython - Mailing list pgsql-general

From DeJuan Jackson
Subject Re: PlPython
Date
Msg-id 3EFB3C12.7050802@speedfc.com
Whole thread Raw
In response to PlPython  (Kevin Jacobs <jacobs@penguin.theopalgroup.com>)
List pgsql-general
So, the issue is that rexec was supposed to be secure but it's not and has be removed from future versions.  Kevin has replace the calls of rexec with a non-secure version (maybe 'exec'), therefore the calls to plpython would be inherently insecure in the first place, so we have to make it an untrusted language.

Correct?

Kevin Jacobs wrote:
On Thu, 26 Jun 2003, DeJuan Jackson wrote: 
Just wondering (I don't use or intend to use plpython), but why does it 
need to be marked untrusted is the rexec code has been corrected.   
No corrected -- removed.   Rexec is and will likely remain broken for at
least one more Python release.  Thus, it was decided to remove all support
for it in Python, and consequently from PlPython.

-Kevin
 

pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: PlPython
Next
From: Mikhail Terekhov
Date:
Subject: Re: PlPython