Research
.
Skip Search Box

SELinux Mailing List

Re: macros/vi

From: Russell Coker <russell_at_coker.com.au>
Date: Tue, 16 Mar 2004 18:33:07 +1100


On Tue, 16 Mar 2004 17:08, "keen@internode.on.net" <keen@internode.on.net> wrote:
> would like to find out is there any technical difference by
> defining TE rules for an application in
> domains/program/app.te and macros/programs/app.te ? When
> would it be better to use it as a macro, or would it be
> better to list it just in the domains directory?

The main reason for the macros/program/ directory is so that macro definitions can be included before anything uses them.

If you have a macro that is only used in one .te file then including it's definition in that .te file is probably best (see ssh.te for an example).

> As a way to learn configuring the policy, I am currently
> still experimenting with configuring TE rules for vi(vim).
> Would it be necessary for vi to run in its own domain as
> such? Or running it under the invoking user's domain would
> suffice?

Why would you want vi to run in it's own domain? What extra access do you want to grant or what of the regular user access do you want to remove?

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page

--
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.
Received on Tue 16 Mar 2004 - 02:34:43 EST
 

Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009

 
bottom

National Security Agency / Central Security Service