Re: Fixing insecure security definer functions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Fixing insecure security definer functions
Date
Msg-id 200704192353.44329.peter_e@gmx.net
Whole thread Raw
In response to Re: Fixing insecure security definer functions  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost wrote:
> While I agree that raising a warning makes sense I don't believe it
> should be forced.  There may be cases where, even in security definer
> functions, the current search_path should be used (though, of course,
> care must be taken in writing such functions).

I really wonder whether such a use case exists.  What would it be?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: "Gustavo Tonini"
Date:
Subject: Fragmentation project
Next
From: Gregory Stark
Date:
Subject: Re: Allowing COPY into views