All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Karl MacMillan <kmacmillan@tresys.com>
Cc: russell@coker.com.au, "'Stephen Smalley'" <sds@epoch.ncsc.mil>,
	selinux@tycho.nsa.gov, selinux-dev@tresys.com
Subject: Re: Now that SELinux supports booleans should we replace tunableswith booleans?
Date: Tue, 10 Aug 2004 10:33:30 -0400	[thread overview]
Message-ID: <4118DCBA.7080104@redhat.com> (raw)
In-Reply-To: <200408101429.i7AET6Sf010692@gotham.columbia.tresys.com>

Karl MacMillan wrote:

>>-----Original Message-----
>>From: Russell Coker [mailto:russell@coker.com.au]
>>Sent: Tuesday, August 10, 2004 2:47 AM
>>To: Stephen Smalley
>>Cc: Karl MacMillan; selinux@tycho.nsa.gov; Daniel J Walsh; selinux-
>>dev@tresys.com
>>Subject: Re: Now that SELinux supports booleans should we replace
>>tunableswith booleans?
>>
>>On Tue, 10 Aug 2004 06:11, Stephen Smalley <sds@epoch.ncsc.mil> wrote:
>>    
>>
>>>>Under the proposed scheme, reboots and policy reloads would set the
>>>>booleans to the values saved in /etc/selinux/$SELINUXTYPE/booleans
>>>>(defaulting to the compile-time defaults if there was no value saved
>>>>        
>>>>
>>in
>>    
>>
>>>>that file for a given boolean).  Admins would edit that file (directly
>>>>or using a tool) if they wanted the boolean setting to persist; if
>>>>        
>>>>
>>they
>>    
>>
>>>>only want a temporary change that will be reverted by a reboot or
>>>>        
>>>>
>>policy
>>    
>>
>>>>reload, then they would use setsebool to make that temporary change.
>>>>        
>>>>
>>>Karl has suggested that while /sbin/init should use this technique for
>>>preserving booleans across reboots, /usr/sbin/load_policy should just
>>>get the current boolean settings from selinuxfs and use them for policy
>>>reloads, so that booleans do not change upon a policy reload by
>>>default.  This is to ensure that booleans that represent system state
>>>are not perturbed by policy reloads.  What do others think?
>>>      
>>>
>>Sounds good.
>>
>>    
>>
>
>Another question is what happens if you change the default value in the
>policy source? Under this suggestion, the new default would not take effect
>until a reboot and then only if the config file doesn't specify the boolean
>value. Not certain if this is a problem, but it is kind of strange and
>potentially surprising to policy authors.
>  
>
Maybe load_policy should log to the syslog which boolean settings it is 
using,  Does the kernel
have any memory of booleans that were manually changed from the default?

Dan

>Karl
>
>Karl MacMillan
>Tresys Technology
>http://www.tresys.com
>(410)290-1411 ext 134
>
>  
>
>>--
>>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.

  reply	other threads:[~2004-08-10 14:33 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 13:59 Now that SELinux supports booleans should we replace tunables with booleans? Daniel J Walsh
2004-04-13 17:09 ` Chris PeBenito
2004-04-13 17:53 ` Tom Mitchell
2004-04-14 13:16   ` Karl MacMillan
2004-04-14 16:19     ` Russell Coker
2004-04-14 17:19       ` Karl MacMillan
2004-04-14 19:50       ` Valdis.Kletnieks
     [not found]         ` <407DF398.4010405@redhat.com>
2004-04-15  5:28           ` Russell Coker
2004-04-15 14:52           ` Valdis.Kletnieks
2004-04-14 19:58       ` James Morris
2004-04-14 20:19         ` James Morris
2004-04-21 16:05         ` Karl MacMillan
2004-04-13 23:17 ` Russell Coker
2004-04-14 13:11   ` Karl MacMillan
2004-04-14 13:30     ` Stephen Smalley
2004-04-14 14:10       ` Now that SELinux supports booleans should we replace tunableswith booleans? Karl MacMillan
2004-04-14 16:00         ` Russell Coker
2004-04-14 13:38     ` Now that SELinux supports booleans should we replace tunables with booleans? Russell Coker
2004-04-14 14:53       ` Karl MacMillan
2004-08-02 18:53         ` Stephen Smalley
2004-08-02 19:08           ` Stephen Smalley
2004-08-05 12:30           ` Stephen Smalley
2004-08-05 12:33             ` Stephen Smalley
2004-08-05 13:44               ` Daniel J Walsh
2004-08-06 14:04                 ` Stephen Smalley
2004-08-06 15:57               ` Now that SELinux supports booleans should we replace tunableswith booleans? Karl MacMillan
2004-08-06 16:20                 ` Stephen Smalley
2004-08-09 20:11                   ` Stephen Smalley
2004-08-10  6:46                     ` Russell Coker
2004-08-10 14:29                       ` Karl MacMillan
2004-08-10 14:33                         ` Daniel J Walsh [this message]
2004-08-10 14:47                           ` Karl MacMillan
2004-08-10 14:43                         ` Stephen Smalley
2004-08-10 17:06                         ` Timothy Wood
2004-08-10 17:20                           ` Stephen Smalley
2004-08-10 13:25                     ` Daniel J Walsh
2004-08-06 14:02           ` Now that SELinux supports booleans should we replace tunables with booleans? Stephen Smalley
2004-08-06 14:20             ` Joshua Brindle
2004-08-06 14:28               ` Stephen Smalley
2004-08-06 14:38                 ` Daniel J Walsh
2004-08-06 15:30                   ` Stephen Smalley
2004-08-06 15:36                   ` kmacmillan
2004-08-06 14:23           ` Stephen Smalley
2004-08-06 14:40             ` Daniel J Walsh
2004-08-06 15:02               ` Stephen Smalley
2004-08-23 19:33                 ` Daniel J Walsh

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=4118DCBA.7080104@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=kmacmillan@tresys.com \
    --cc=russell@coker.com.au \
    --cc=sds@epoch.ncsc.mil \
    --cc=selinux-dev@tresys.com \
    --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.