Re: unconfined_t Domain with MLS Policy

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

 



On Tue, 2008-03-18 at 11:31 -0700, Henley, Tim-P64420 wrote:
> Is the unconfined_t Domain available when running with the MLS Policy?
> I was attempting to assign a Perl script to the domain using chcon
> (with the -t switch). The result is that I get an "Invalid argument"
> error message. I'm doing this on a development box (the Perl script is
> for dev use only) as a means of trying to avoid having to stop and
> write a policy for every script/executable I create during
> development. Is this how I should be handling this or is there a more
> appropriate way to do this? Thanks in advance.

unconfined_t is generally only present in -targeted policy, not -strict
or -mls, although one can build it into any policy.

But the bigger question is why you think you need to roll a policy for
every script/executable - you should only need to introduce a separate
domain when the program requires a different set of permissions than its
caller, and in many cases, you can just use an existing domain for a
related program that requires similar access.  For user programs, most
of them should just run in the user's domain without a problem.

-- 
Stephen Smalley
National Security Agency


--
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