All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: selinux@tycho.nsa.gov, Russell Coker <russell@coker.com.au>,
	selinux-dev@tresys.com
Subject: Re: Now that SELinux supports booleans should we replace tunables with booleans?
Date: Mon, 23 Aug 2004 15:33:25 -0400	[thread overview]
Message-ID: <412A4685.5000307@redhat.com> (raw)
In-Reply-To: <1091804570.8590.80.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:

>On Fri, 2004-08-06 at 10:40, Daniel J Walsh wrote:
>  
>
>>I have not studied the booleans that closely.  But I it seems to me that 
>>booleans are something
>>that Admins would like to work with, versus tunables being something 
>>that distributions are going
>>to make decisions on.  Of course it is not that clean.  The  best thing 
>>about booleans is that the source
>>code is not required.
>>
>>I think there are several tunables that can be removed.
>>    
>>
>
>Ok, so it would be helpful to review the current set of booleans and
>tunables to see how well they match up against this general criteria,
>and to also check which ones can be removed entirely.  The present
>breakdown is really only based on whether or not the existing tunable
>could be easily converted to a boolean (i.e. only covered TE avtab
>rules, relatively localized, small number of affected rules).
>
>Current set of booleans (strict policy) are:
>allow_xserver_home_fonts
>cron_can_relabel
>ftpd_is_daemon
>ftp_home_dir
>httpd_enable_cgi
>httpd_enable_homedirs
>httpd_ssi_exec
>mozilla_readhome
>mozilla_writehome
>named_write_master_zones
>read_default_t
>run_ssh_inetd
>secure_mode
>ssh_sysadm_login
>staff_read_sysadm_file
>user_direct_mouse
>user_dmesg
>user_ping
>user_rw_noexattrfile
>user_rw_usb
>user_tcp_server
>user_ttyfile_stat
>xdm_sysadm_login
>
>Current set of policy tunables are:
>nscd_all_connect
>user_net_control
>user_can_mount
>unlimitedRPM
>unlimitedUtils
>nfs_home_dirs
>use_games
>allow_ypbind
>unlimitedRC
>direct_sysadm_daemon
>hide_broken_symptoms
>unrestricted_admin
>nfs_export_all_rw
>unlimitedUsers
>nfs_export_all_ro
>user_canbe_sysadm
>unlimitedInetd
>
>  
>
I think we can get rid of unlimitedUsers, you really should run targeted 
policy for this.
single_userdomain should also be removed since I don't think anyone has 
run it and they should use targeted policy.
I am not sure unrestricted_admin is needed although this has been turned 
on in Fedora Policy.
nfs_export_all should be made one tunable and then have a boolean to 
allow RW or not.


--
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-23 19: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
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 [this message]

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=412A4685.5000307@redhat.com \
    --to=dwalsh@redhat.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.