|Main Archive Page > Month Archives > selinux archives|
On Wed, 2007-08-22 at 07:13 -0400, Stephen Smalley wrote:
> On Tue, 2007-08-21 at 16:58 -0400, Daniel J Walsh wrote:
> > James Carter wrote:
> > > Why isn't the Makefile and other information needed to build a module
> > > separately in the appropriate /usr/share/selinux/<policy name>
> > > directory? This seems like the logical place for that information. The
> > > (not very well documented) "install-headers" make target in the
> > > refpolicy Makefile does this.
Sorry, I was out of the office last week. I'll add some docs about setting up a policy module build via headers.
> > > Instead, the information to build a module for Fedora is in
> > > the /usr/share/selinux/devel directory. This directory would seem to be
> > > independent of the policy type, even though it is only for building
> > > Fedora policies. This seems confusing. The devel directory should have
> > > stuff that all policies need or could use.
> > >
> > > Wouldn't it make sense that if I wanted to build a module for the
> > > current policy, I would use the Makefile in devel which would look
> > > at /etc/selinux/config and include the Makefile for the current policy,
> > > but if I wanted to compile for a particular policy, I would just use the
> > > Makefile in its /usr/share directory?
> > >
> > >
> > This is an old argument, between strict and targeted policy. I did not
> > like the idea of building
> > policy modules different for each type of policy, Since almost everyone
> > is exactly the same or would not work on different policies. This seems
> > to be proven to be correct as we move to strict/targeted policy merge.
> > So you add a level of complexity with very little value. Just imagine a
> > third party shipping multiple policies for the
> > same package depending on an infinite number of policy packages.
> > targeted, strict, mls, olpc, CDS-ABC.
> > And almost guaranteed the same policy package would work for all or the
> > package will only really work on one (MLS). So I went with the least
> > common denominator and only ship one devel package. All interfaces for
> > all packages ship.
> But does this allow people using a policy other than targeted to build
> loadable modules using the /usr/share/selinux/devel/Makefile? Or do
> they have to separately install refpolicy to do that? That's the
> problem, IIUC.
It works because the headers are currently the same between the policy types. The only thing needed to change the behavior are the usual build.conf settings. Refpolicy upstream has the separate dirs in /usr/share/selinux in case that changes, or 3rd parties want different implementations per type. Also it has a copy of the build.conf so the infrastructure doesn't have to try to determine the right settings. -- Chris PeBenito Tresys Technology, LLC (410) 290-1411 x150 -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to email@example.com with the words "unsubscribe selinux" without quotes as the message.