Re: SE-PostgreSQL Specifications - Mailing list pgsql-hackers

From KaiGai Kohei
Subject Re: SE-PostgreSQL Specifications
Date
Msg-id 4A6BD021.7010503@kaigai.gr.jp
Whole thread Raw
In response to Re: SE-PostgreSQL Specifications  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas wrote:
> On Sat, Jul 25, 2009 at 11:27 PM, KaiGai Kohei<kaigai@kaigai.gr.jp> wrote:
>> | Access control is conceptually to decide a set of allowed (or denied)
>> | actions between a certain subject (such as a database client) and an
>> | object (such as a table), and to apply the decision on user's requests.
>> | At the database privilege system, ACL stored in database objects itself
>> | holds a list of allowed actions to certain database roles, and it is
>> | applied on the user's request.
>> | SELinux also holds massive sets of allowed actions between a certain
>> | subject and a certain object, we call them security policy.
>>
>> Is it obscure?
> 
> It's obscure to me.  :-)
> 
> I think you need to define security policy more precisely and give at
> least one or two examples of security policy entries.

OK, I'll try to define it more precisely and introduce a few examples
in the documents.

Thanks,
-- 
KaiGai Kohei <kaigai@kaigai.gr.jp>


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Patch for 8.5, transformationHook
Next
From: Robert Haas
Date:
Subject: Re: SE-PostgreSQL Specifications