Re: [PATCH] Fix leaky VIEWs for RLS - Mailing list pgsql-hackers

From KaiGai Kohei
Subject Re: [PATCH] Fix leaky VIEWs for RLS
Date
Msg-id 4C0D9861.9050201@ak.jp.nec.com
Whole thread Raw
In response to Re: [PATCH] Fix leaky VIEWs for RLS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Fix leaky VIEWs for RLS  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
(2010/06/08 9:46), Tom Lane wrote:
> KaiGai Kohei<kaigai@ak.jp.nec.com>  writes:
>> In this case, is it unnecessary to expose the given argument in
>> the error message (from security perspective), isn't it?
> 
> Yes, if all you care about is security and not usability, that looks
> like a great solution.  We're *not* doing it.
> 
Sorry, are you saying we should not revise error messages because
of usability??

If so, and if we decide the middle-threat also should be fixed,
it is necessary to distinguish functions trusted and untrusted,
even if a function is built-in.
Perhaps, pg_proc takes a new flag to represent it.

Thanks,
-- 
KaiGai Kohei <kaigai@ak.jp.nec.com>


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: [PATCH] Fix leaky VIEWs for RLS
Next
From: Stephen Frost
Date:
Subject: Re: [PATCH] Fix leaky VIEWs for RLS