From: Justin Smith <jsmith@mcs.drexel.edu>
To: Stephen Smalley <sds@tislabs.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: simple Perl script to converse messages to access rules
Date: 04 Dec 2001 09:32:43 -0500 [thread overview]
Message-ID: <1007476363.2135.0.camel@jsmith.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0112040913380.28408-100000@raven>
On Tue, 2001-12-04 at 09:24, Stephen Smalley wrote:
> While this script should be helpful in customizing the policy
> configuration, you should carefully examine its output to ensure that the
> resulting rules do not violate your security objectives. Frequently,
> rather than granting the permission between the existing domain and type,
> you will want to define a new domain for the process and/or a new type for
> the file and only grant the permission for the new domain and/or type.
>
> --
> Stephen D. Smalley, NAI Labs
> ssmalley@nai.com
>
>
I envisioned this script as a quick and dirty way to get a system
working in enforcing mode AFTER one has defined a bunch of new domains
(that trigger lots of denied messages).
Naturally users should examine the output of this script to confirm that
it will do what they want.
One great thing about SELinux is that it gives a detailed account of
what is taking place in a system. For instance, I discovered that web
users were trying to access files over symbolic links via my web server.
I hadn't been aware that my web server had symbolic link access enabled.
--
--
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 prev parent reply other threads:[~2001-12-04 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 13:57 simple Perl script to converse messages to access rules Justin Smith
2001-12-04 14:24 ` Stephen Smalley
2001-12-04 14:32 ` Justin Smith [this message]
2001-12-04 14:36 ` [PATCH] AVC auditing changes 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=1007476363.2135.0.camel@jsmith.org \
--to=jsmith@mcs.drexel.edu \
--cc=sds@tislabs.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.