From: | KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Sam Mason <sam(at)samason(dot)me(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SE-PostgreSQL Specifications |
Date: | 2009-07-26 03:40:17 |
Message-ID: | 4A6BD021.7010503@kaigai.gr.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
> On Sat, Jul 25, 2009 at 11:27 PM, KaiGai Kohei<kaigai(at)kaigai(dot)gr(dot)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(at)kaigai(dot)gr(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-07-26 03:44:24 | Re: SE-PostgreSQL Specifications |
Previous Message | Pavel Stehule | 2009-07-26 03:38:25 | Re: Patch for 8.5, transformationHook |