Re: security label support, part.2
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: KaiGai Kohei <kaigai@ak.jp.nec.com>, Tom Lane <tgl@sss.pgh.pa.us>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, KaiGai Kohei <kaigai@kaigai.gr.jp>, pgsql-hackers@postgresql.org
Date: 2010-08-18T12:54:48Z
Lists: pgsql-hackers
On Wed, Aug 18, 2010 at 8:49 AM, Stephen Frost <sfrost@snowman.net> wrote: > In the end, I'm thinking that if the external security module wants to > enforce a check against all the children of a parent, they could quite > possibly handle that already and do it in such a way that it won't break > depending on the specific query. To wit, it could query the catalog to > determine if the current table is a parent of any children, and if so, > go check the labels/permissions/etc on those children. I'd much rather > have something where the permissions check either succeeds or fails > against the parent, depending on the permissions of the parent and its > children, than on what the query is itself and what conditionals are > applied to it. Interesting idea. Again, I haven't read the code, but seems worth further investigation, at least. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company