From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bradley McLean <brad(at)bradm(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Possible major bug in PlPython (plus some other ideas) |
Date: | 2001-11-13 21:17:15 |
Message-ID: | 3608.1005686235@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bradley McLean <brad(at)bradm(dot)net> writes:
> (Everyone) Would a patch to add trusted language support be accepted
> for 7.2, or is it too late?
I think the code in there already is the trusted case, no? The addition
would be an untrusted mode for plpython.
trusted = language handler prevents security violations, so unprivileged
users are allowed to define functions in the language (ie, we trust the
language itself to prevent security breaches)
untrusted = language allows user to access things outside database,
so only Postgres superusers are allowed to define functions in the
language (ie, we must trust the function author instead of the language)
In any case, a second security level in plpython would clearly be a new
feature, and so I'd say it's too late to consider it for 7.2. All that
we want to do at this point is verify Kevin's proposed patch for the
existing security level. But certainly a "plpythonu" addition would
be welcome for 7.3.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Liam Stewart | 2001-11-13 21:28:57 | Re: Funny timezone shift causes failure in test suite |
Previous Message | Marc G. Fournier | 2001-11-13 20:08:02 | Re: Remember to register PostgreSQL for JDJ 2002 awards (fwd) |