All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: SELinux <SELinux@tycho.nsa.gov>
Subject: There are several file_contexts that users might want to set in order to share data.
Date: Fri, 07 Jan 2005 16:45:22 -0500	[thread overview]
Message-ID: <41DF02F2.5090503@redhat.com> (raw)

I have added a configurable attribute (Need a better name).  So the 
policy writer could identify these files.

type httpd_sys_content_t, file_type,  httpdcontent, sysadmfile, 
configurable;
type httpd_sys_script_exec_t, file_type, sysadmfile, configurable;
type httpd_sys_script_ro_t, file_type, httpdcontent, sysadmfile, 
configurable;
type httpd_sys_script_rw_t, file_type, httpdcontent, sysadmfile, 
configurable;
type httpd_sys_script_ra_t, file_type, httpdcontent, sysadmfile, 
configurable;
type ftpd_anon_t, file_type, sysadmfile, configurable;
type samba_share_t, file_type, sysadmfile, configurable;

Then we could have something extract the fields out of policy and some 
how get this info to the users.
The question comes up since someone is starting to use samba to share 
files and they did not know what to set the data too.
The people documenting it would have no way of knowing without studying 
the policy. 

Ideas???

Maybe if we added this flag we could have setfiles/restorecon look at it 
and not change any files that have these context.  I know we already 
discussed this.

--
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-01-07 21:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41DF02F2.5090503@redhat.com \
    --to=dwalsh@redhat.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.