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: security label support, part.2 |
Date: | 2010-08-25 05:38:30 |
Message-ID: | 4C74AC56.5050806@ak.jp.nec.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>> 7. I think we need to write and include in the fine documentation some
>>>> "big picture" documentation about enhanced security providers. Of
>>>> course, we have to decide what we want to say. But the SECURITY LABEL
>>>> documentation is just kind of hanging out there in space right now; it
>>>> needs to connect to a broad introduction to the subject.
>>>>
>>> OK, I'll try to describe with appropriate granularity.
>>> Do we need an independent section in addition to the introduction of
>>> SECURITY LABEL syntax?
>>
>> I think so. I suggest a new chapter called "Enhanced Security
>> Providers" just after "Database Roles and Privileges".
>>
> OK,
>
Now I'm under describing the new chapter.
http://git.postgresql.org/gitweb?p=users/kaigai/sepgsql.git;a=blob;f=doc/src/sgml/esp.sgml;hb=devel/seclabel
However, I'm wondering whether the topic about security hooks and some
others are appropriate for the "III. Server Administration" part.
Perhaps, it is a good idea a new section at the last of "Database Roles
and Privileges" which introduce a fact that PostgreSQL allows plugins
to make access control decision, and a new chapter in the "VII. Internals"
part.
How about the idea?
Thanks,
--
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-08-25 06:26:51 | Re: gSoC add MERGE command new patch -- merge_v104 |
Previous Message | Itagaki Takahiro | 2010-08-25 05:34:56 | Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP) |