Re: [ANNOUNCE] Advisory on possibly insecure security definer functions - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: [ANNOUNCE] Advisory on possibly insecure security definer functions
Date
Msg-id 20070217141525.GC4468@merkur.hilbert.loc
Whole thread Raw
In response to Re: [ANNOUNCE] Advisory on possibly insecure security definer functions  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: [ANNOUNCE] Advisory on possibly insecure security definer functions
List pgsql-general
On Sat, Feb 17, 2007 at 01:26:34PM +0900, Tatsuo Ishii wrote:

> But if we insert a set schema search_path command in an SQL function,
> the caller will be affected by it. Doing reset search_path before
> returning to caller might solve some of problems, but it will not
> recover caller's special search_path. How do you solve the problem?

Schema-qualifying object accesses would be tedious,
omission-prone but not liable to the above problem.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

pgsql-general by date:

Previous
From: "Alexi Gen"
Date:
Subject: pg_tablespace.spcacl
Next
From: Alvaro Herrera
Date:
Subject: Re: pg_tablespace.spcacl