| From: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] SE-PgSQL/lite rev.2163 |
| Date: | 2009-07-16 02:38:02 |
| Message-ID: | 4A5E928A.50705@ak.jp.nec.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> 2009/7/14 KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>:
>> On the other hand, db_schema class was designed as an analogy to
>> directoty in filesystems. SELinux defines several permissions on
>> "dir" object class, such as "add_name", "remove_name" and "search".
>
> I think that's a bad analogy and you need to make the permission names
> match the way PostgreSQL handles schema permissions generally.
> There's only so many times and ways to says this...
OK...
I can replace "search" by "usage".
Do you have any alternative ideas for "add_name" and "remove_name"?
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2009-07-16 03:05:23 | [PATCH] SE-PgSQL/tiny rev.2193 |
| Previous Message | Robert Haas | 2009-07-16 02:11:23 | Re: [PATCH] SE-PgSQL/lite rev.2163 |