Re: RLS open items are vague and unactionable - Mailing list pgsql-hackers

From Noah Misch
Subject Re: RLS open items are vague and unactionable
Date
Msg-id 20151120081136.GA1486542@tornado.leadboat.com
Whole thread Raw
In response to Re: RLS open items are vague and unactionable  (Stephen Frost <sfrost@snowman.net>)
Responses Re: RLS open items are vague and unactionable  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Mon, Sep 28, 2015 at 03:03:51PM -0400, Stephen Frost wrote:
> If SELECT rights are required then apply the SELECT policies, even if
> the actual command is an UPDATE or DELETE.  This covers the RETURNING
> case which was discussed previously, so we don't need the explicit check
> for that, and further addresses the concern raised by Zhaomo about
> someone abusing the WHERE clause in an UPDATE or DELETE.
> 
> Further, if UPDATE rights are required then apply the UPDATE policies,
> even if the actual command is a SELECT.  This addresses the concern that
> a user might be able to lock rows they're not actually allowed to UPDATE
> through the UPDATE policies.
> 
> Comments welcome, of course.  Barring concerns, I'll get this pushed
> tomorrow.

The CREATE POLICY reference page continues to describe the behavior this patch
replaced, not today's behavior.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Error with index on unlogged table
Next
From: Marko Tiikkaja
Date:
Subject: Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)