From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <465ECD72.1070809@kaigai.gr.jp> Date: Thu, 31 May 2007 22:28:18 +0900 From: KaiGai Kohei MIME-Version: 1.0 To: Eamon Walsh CC: KaiGai Kohei , Joshua Brindle , "Christopher J. PeBenito" , Stephen Smalley , SELinux Mail List Subject: Re: object class discovery userland References: <1177077717.15762.32.camel@sgc> <4628F05B.7040309@tycho.nsa.gov> <4628F20E.2000208@tycho.nsa.gov> <1177089541.24870.17.camel@sgc> <1177338792.24282.16.camel@moss-spartans.epoch.ncsc.mil> <6FE441CD9F0C0C479F2D88F959B01588A71927@exchange.columbia.tresys.com> <1177340283.24282.24.camel@moss-spartans.epoch.ncsc.mil> <1179929852.10995.51.camel@sgc.columbia.tresys.com> <46548D4E.50000@tycho.nsa.gov> <465623DD.6090304@tycho.nsa.gov> <6FE441CD9F0C0C479F2D88F959B01588BEFF31@exchange.columbia.tresys.com> <465750DF.1050509@tycho.nsa.gov> <465CDF54.9050300@ak.jp.nec.com> <465DD820.70005@tycho.nsa.gov> In-Reply-To: <465DD820.70005@tycho.nsa.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov > I think that because of the heavy customization in the Postgres AVC > implementation it is best kept outside-of-tree at the current time. OK, > There are other applications that use process pools such as Apache and > if these become hosts to object managers then it may be useful to > provide a shared memory option in the libselinux version. The solution > would involve a flag to the init function, some method of providing the > shared memory segment to attach to, and special functionality for the > "manager" process that will listen on netlink. Can I consider those features as a future todo? Or, do you want to have a discussion in this chance? > However, the Postgres implementation is not fully "shared memory" based. > The SID-to-context mapping is kept in a "pg_selinux" database table > which is not stored in shared memory but rather is mapped from disk > (correct me if I'm wrong). It's correct. SE-PostgreSQL leverages one of the subsystems provided by native PostgreSQL, to implement SID-to-context mapping. It is not based on share memory directly. > In the previous thread, the possibility of > providing callbacks for doing the SID-to-context mapping was discussed. > However IMO if this part of the library has to be outsourced to the > application then the application might as well do the entire AVC. I agrees your opinion. In the case that applications can handle SID-to-context mapping well, those works should be outsourced and being detachable from libselinux's AVC. In my case, an idea using PostgreSQL's Oid (Object Identifier) as a persistent SID works well :) Thanks, -- KaiGai Kohei -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.