From: Murray McAllister <mmcallis@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>,
Daniel Walsh <dwalsh@redhat.com>, Eric Paris <eparis@redhat.com>,
James Morris <jmorris@namei.org>,
Dominick Grift <domg472@gmail.com>
Subject: Re: user guide drafts: "Linux Permissions" and "Manual Pages for Services"
Date: Thu, 13 Nov 2008 15:11:10 +1000 [thread overview]
Message-ID: <491BB6EE.9010909@redhat.com> (raw)
In-Reply-To: <1226503901.21407.19.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2008-11-12 at 11:49 +1000, Murray McAllister wrote:
>> Hi,
>>
>> The following are drafts for the "Fixing Problems"[1] section. Any
>> comments and corrections are appreciated.
>>
>> Linux Permissions
>>
>> When access is denied, check standard Linux permissions. As mentioned in
>> Chapter 2, Introduction, most operating systems use a Discretionary
>> Access Control (DAC) system to control access, allowing users to control
>> the permissions of files that they own. SELinux policy rules are checked
>> after DAC rules. SELinux policy rules are not used if DAC rules deny
>> access first.
>>
>> If access is denied and no SELinux denials are logged,
>
> Logically you would also mention the dontaudit case here, and how to
> check for denials hidden by dontaudit rules.
>
How about (keeping in mind I have not really heard of this before):
dontaudit Rules and Linux Permissions
Bugs in applications may cause a lot of SELinux denials, but such
denials may not prevent the application from running correctly. For
these situations, dontaudit rules can be added to policy to prevent log
files being filled with denial messages. The downside of this is that,
although SELinux denies access, denial messages are not logged, making
troubleshooting hard.
To temporarily disable dontaudit rules, allowing all denials to be
logged, run the following command as the Linux root user:
/usr/sbin/semodule -DB
The -D option disables dontaudit rules; the -B option rebuilds policy.
The dontaudit rules are disabled until policy is rebuilt. To rebuild
policy and enable dontaudit rules, run the following command as the
Linux root user:
/usr/sbin/semodule -B
For a full list of dontaudit rules, run the sesearch --dontaudit
command. Narrow down searches using the -s domain option and the grep
command. For example:
[output from "sesearch --dontaudit -s smbd_t | grep squid
"]
Refer to Section 7.3.5, “Raw Audit Messages” and Section 7.3.6, “sealert
Messages” for information about analyzing denials.
After resolving any issues found by removing dontaudit rules, or if
disabling these rules did not produce denials for your situation, check
standard Linux permissions. [rest of Linux Permissions content].
Thanks.
--
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.
next prev parent reply other threads:[~2008-11-13 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 1:49 user guide drafts: "Linux Permissions" and "Manual Pages for Services" Murray McAllister
2008-11-12 15:31 ` Stephen Smalley
2008-11-13 5:11 ` Murray McAllister [this message]
2008-11-13 12:59 ` 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=491BB6EE.9010909@redhat.com \
--to=mmcallis@redhat.com \
--cc=domg472@gmail.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--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.