All of lore.kernel.org
 help / color / mirror / Atom feed
From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: SELinux List <selinux@tycho.nsa.gov>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Karl MacMillan <kmacmillan@mentalrootkit.com>,
	Joshua Brindle <jbrindle@tresys.com>
Subject: Re: RFC: Per-object manager controls in /selinux/config
Date: Thu, 20 Dec 2007 14:01:37 +0900	[thread overview]
Message-ID: <4769F731.6050002@ak.jp.nec.com> (raw)
In-Reply-To: <4769A947.1030403@tycho.nsa.gov>

Eamon Walsh wrote:
> I am proposing adding a separate config line for each userspace object 
> manager, as follows:
> 
> #    permissive - SELinux prints warnings instead of enforcing.
> #    disabled - SELinux is fully disabled.
> SELINUX=enforcing
> +
> +# SELINUX_MANAGER= can take one of these four values
> +#    enforcing - SELinux security policy is enforced by this object 
> manager.
> +#    permissive - The object manager prints warnings instead of enforcing.
> +#    disabled - SELinux is fully disabled by this object manager.
> +#    default - The object manager will track the system setting.
> +SELINUX_DBUS=default
> +SELINUX_XSERVER=permissive
> +
> # SELINUXTYPE= type of policy in use. Possible values are:
> #    targeted - Only targeted network daemons are protected.
> #    strict - Full SELinux protection.

Eamon,

Could you tell me the purpose of this new feature?

It seems to me this new feature prevents to keep consistency of
the SELinux state. I think the internal state of userspace object
managers should be just a copy from the in-kernel reference monitor...

Thanks,

> However, I am a little unclear on how runtime setenforce calls should be 
> dealt with.  The way it currently works is if the userspace object 
> manager is initialized without an enforcing mode specified in the call 
> to avc_open(), it will track the system setting and conform to netlink 
> "setenforce" messages.  However, if avc_open() is called with an 
> enforcing mode specified, it will stay in that mode and not respond to 
> the netlink messages.  Users might thus be confused if they issue a 
> "setenforce 0" and the X server stays in enforcing mode because it was 
> specified that way in the config file.  But I'm of the opinion that 
> runtime setenforcing is an abnormal event, and anyone who edits the 
> config file away from "default" and then runs setenforce will understand 
> how it works.

-- 
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>

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

  reply	other threads:[~2007-12-20  5:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 23:29 RFC: Per-object manager controls in /selinux/config Eamon Walsh
2007-12-20  5:01 ` KaiGai Kohei [this message]
2007-12-20  6:03   ` Joshua Brindle
2008-06-04  4:35   ` KaiGai Kohei
2008-06-05 19:12     ` Eamon Walsh
2008-06-05 19:49       ` Stephen Smalley
2008-06-06  6:13         ` KaiGai Kohei
2008-06-06 12:52           ` Stephen Smalley
2008-06-09 11:09             ` KaiGai Kohei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4769F731.6050002@ak.jp.nec.com \
    --to=kaigai@ak.jp.nec.com \
    --cc=ewalsh@tycho.nsa.gov \
    --cc=jbrindle@tresys.com \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.