Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep)
От | KaiGai Kohei |
---|---|
Тема | Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep) |
Дата | |
Msg-id | 48D3D7E1.2010207@kaigai.gr.jp обсуждение исходный текст |
Ответ на | Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep) ("Robert Haas" <robertmhaas@gmail.com>) |
Ответы |
Re: Proposal of SE-PostgreSQL patches (for CommitFest:Sep)
|
Список | pgsql-hackers |
Robert Haas wrote: >> [2] Make a new implementation of OS-independent fine grained access control >> >> If it is really really necessary, I may try to implement a new separated >> fine-grained access control mechanism due to the CommitFest:Nov. >> However, we don't have enough days to develop one more new feature from >> the scratch by the deadline. > > +1. > > ...Robert It's too early to vote. :-) The second and third option have prerequisite. The purpose of them is to match granularity of access controls provided by SE-PostgreSQL and native PostgreSQL. However, I have not seen a clear reason why these different security mechanisms have to have same granuality in access controls. As I mentioned before, it is quite natural that different security mechanism provides its access controls in different granuality, as widely accepted in Linux. The reason is now unclear for me. Thanks, -- KaiGai Kohei <kaigai@kaigai.gr.jp>
В списке pgsql-hackers по дате отправления: