From: Justin Smith <jsmith@mcs.drexel.edu>
To: selinux@tycho.nsa.gov
Subject: policy additions needed to make my system run in secure mode
Date: 01 Dec 2001 10:21:26 -0500 [thread overview]
Message-ID: <1007220086.2747.0.camel@jsmith.org> (raw)
These are lines of text I had to ADD to the default NSA policy to
allow my system to boot and run its normal functions in secure mode:
(I haven't tested X windows and my usual desktop environment yet,
so there may be more such additions...)
------------------------------------------------------------------------
initrc.te:
# ipchains
allow initrc_t initrc_t:rawip_socket { create setopt };
# usb
allow initrc_t unlabeled_t:dir { search };
allow initrc_t unlabeled_t:file { read getattr };
allow mount_t usr_t:dir { mounton };
allow mount_t usr_t:file { append setattr };
allow mount_t proc_t:dir { mounton };
# postgres
allow initrc_t user_home_t:dir { append };
allow initrc_t user_home_t:file { append };
allow initrc_t var_lib_t:dir { write add_name create };
allow initrc_t var_lib_t:file { create };
allow initrc_t tmpfs_t:file { read write };
--------------------------------------------------------------------------
apache.te:
# General (allow server-side includes)
allow httpd_t httpd_user_script_rw_t:file { getattr read };
#
# Servlets
# (I modified file types to make all my web pages t
# httpd_user_script_rw_t
# and the Tomcat servlet directory to httpd_user_script)
#
allow httpd_t httpd_user_script_t:file { append };
allow initrc_t httpd_user_script_rw_t:dir
{ getattr search };
allow httpd_t httpd_user_script_rw_t:dir
{ search getattr };
allow initrc_t httpd_user_script_rw_t:file
{ read getattr append write };
allow initrc_t httpd_user_script_t:dir { read write };
allow initrc_t httpd_user_script_t:file
{ read write execute execute_no_trans setattr append };
allow initrc_t file_t:lnk_file { read };
allow initrc_t file_t:file { execute execute_no_trans };
allow initrc_t usr_t:file { execute execute_no_trans };
allow initrc_t http_port_t:tcp_socket { name_bind };
--------------------------------------------------------------
user.te:
# Postgres
allow user_t usr_t:file { execute execute_no_trans };
allow user_t initrc_tmp_t:sock_file { write };
allow user_t initrc_t:unix_stream_socket { connect };
----------------------------------------------------------
These may not be ideal from a security point of view but they work.
--
--
You have received this message because you are subscribed to the selinux 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.
next reply other threads:[~2001-12-01 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 15:21 Justin Smith [this message]
2001-12-03 14:52 ` policy additions needed to make my system run in secure mode Stephen Smalley
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=1007220086.2747.0.camel@jsmith.org \
--to=jsmith@mcs.drexel.edu \
--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.