All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Ivan Gyurdiev <ivg2@cornell.edu>,
	Karl MacMillan <kmacmillan@tresys.com>,
	selinux@tycho.nsa.gov, SELinux-dev@tresys.com
Subject: Re: [RFC][PATCH] New interface for loading policy
Date: Fri, 30 Sep 2005 16:26:11 -0400	[thread overview]
Message-ID: <433D9F63.1080101@redhat.com> (raw)
In-Reply-To: <1128100586.12459.178.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Fri, 2005-09-30 at 08:21 -0400, Stephen Smalley wrote:
>   
>> BTW, one thing that I'm not clear on is how the preservebools case (the
>> default behavior for load_policy) will be handled in the future.  The
>> idea is that if a boolean has been toggled at runtime without altering
>> its saved value (e.g. manually by an admin, or by a cron job that
>> toggles a boolean to enforce different day/night policies, or by an IDS
>> in response to an event), we don't want a subsequent policy reload (e.g.
>> from an update) to reset that boolean value to the saved settings.  At
>> present, load_policy (and thus selinux_mkload_policy) grab the active
>> boolean settings from selinuxfs and patch them into the binary policy
>> image via sepol_genbools_array() by default (preservebools=1).
>>     
>
> We seem to have agreed to drop the optional path argument entirely from
> selinux_mkload_policy().  But we still need to decide whether the
> preservebools argument is going to make sense going forward.  This is
> for preserving temporary boolean values across a policy reload rather
> than resetting them to the policy settings and is the default behavior
> for load_policy (in the absence of the -b option), as noted above.  As
> with the path argument, this argument is not needed for the initial
> policy load by init, but is only relevant for policy reloads.
>
>   
I think you need this behavior for reloads.  Or default to always saving 
the previous state, and
forcing me to use setsebool to change particular defaults.

Dan
-- 



--
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:[~2005-09-30 20:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 21:20 [RFC][PATCH] New interface for loading policy Stephen Smalley
2005-09-29 21:38 ` Daniel J Walsh
2005-09-30  3:48 ` Ivan Gyurdiev
2005-09-30 12:21   ` Stephen Smalley
2005-09-30 12:35     ` Stephen Smalley
2005-09-30 17:16     ` Stephen Smalley
2005-09-30 20:26       ` Daniel J Walsh [this message]
2005-10-03 12:56       ` Karl MacMillan
2005-10-03 14:17         ` Stephen Smalley
2005-10-04 12:41           ` Karl MacMillan
2005-10-03 13:48     ` Karl MacMillan
2005-10-03 14:22       ` Stephen Smalley
2005-10-03 14:37         ` Daniel J Walsh
2005-10-03 14:40         ` Karl MacMillan
2005-10-03 15:41           ` Stephen Smalley
2005-10-03 19:01             ` Stephen Smalley
2005-10-05 14:10               ` Stephen Smalley
2005-10-05 21:12               ` Stephen Smalley
2005-10-06 16:39                 ` Stephen Smalley
2005-09-30 12:51   ` Daniel J Walsh
2005-09-30 14:53 ` Karl MacMillan
2005-09-30 14:59   ` Stephen Smalley
2005-09-30 16:28     ` Karl MacMillan

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=433D9F63.1080101@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=SELinux-dev@tresys.com \
    --cc=ivg2@cornell.edu \
    --cc=kmacmillan@tresys.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.