| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gerhard Häring <gh(at)ghaering(dot)de> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PlPython |
| Date: | 2003-06-30 05:08:37 |
| Message-ID: | 27896.1056949717@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
=?ISO-8859-1?Q?Gerhard_H=E4ring?= <gh(at)ghaering(dot)de> writes:
> ... because most rexec problems are because
> of the new-style classes in Python 2.2 and later, I asked on
> comp.lang.python wether it was safe with 2.1 and earlier.
> Martin von Lwis told me it probably wasn't in
> http://groups.google.com/groups?selm=m3y8ztib79.fsf%40mira.informatik.hu-berlin.de
Hmm. I don't think the second bug mentioned there applies to us (if our
use of rexec allows the Python code to write any file anywhere, it's
already lost its right to trusted status IMHO). But the first one looks
like a killer:
http://sourceforge.net/tracker/?group_id=5470&atid=105470&func=detail&aid=577530
According to that discussion, this bug does exist in Python 1.5 :-(
... so Hannu's argument rests on a false premise anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-06-30 07:30:47 | Re: [HACKERS] PlPython |
| Previous Message | Gerhard Häring | 2003-06-30 04:39:30 | Re: PlPython |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-06-30 07:30:47 | Re: [HACKERS] PlPython |
| Previous Message | Brett Schwarz | 2003-06-30 04:40:54 | Re: libpgtcl and pgtclsh |