Re: Use of optional_policy in templates (compiler bug or feature?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Oct 15, 2008, at 1:46 PM, Christopher J. PeBenito wrote:

On Wed, 2008-10-15 at 11:02 -0500, Joe Nall wrote:
Is it legitimate to define a type within an optional_policy within a
template?

Yes.

I ask because there are a number of compile issues with policy that
look like:

template(`wm_domain_template',`
...
        optional_policy(`
                dbus_system_bus_client_template($1_wm,$1_wm_t)
# does not compile
#               dbus_user_bus_client_template($1,$1_wm,$1_wm_t)
        ')
...
')

I can't reproduce this by just adding it to a random module; there are
likely more factors that just the above template calls.

Using stock Fedora targeted policy:

policy_module(swo,1.0.0)

userdom_unpriv_user_template(swo)
dbus_chat_user_bus(swo,swo_t)

joe



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux