From: Daniel J Walsh <dwalsh@redhat.com>
To: Robert Story <rstory@sparta.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: setroubleshoot problems with MLS policy in enforcing mode
Date: Thu, 04 Sep 2008 09:06:20 -0400 [thread overview]
Message-ID: <48BFDD4C.50105@redhat.com> (raw)
In-Reply-To: <20080827155839.08c93565@sparta.com>
Robert Story wrote:
> Hi,
>
> I'm having some issues with enforcing mode for the MLS policy. I've
> been able to get around a few issues by simply feeding avcs through
> audit2allow, but this is and MLS range issue, so I think something else
> is needed... Here is the AVC
>
> type=AVC msg=audit(1219865658.259:224923): avc: denied { write } for pid=1332 comm="audispd" path="socket:[7463]" dev=sockfs ino=7463 scontext=system_u:system_r:audisp_t:s15:c0.c1023 tcontext=system_u:system_r:audisp_t:s0-s15:c0.c1023 tclass=unix_stream_socket
>
> This message is repeated quite frequently, driving the load up and
> filling the log file. The audispd processing is running at SystemHigh,
> and I haven't found a way to kill it without dropping to permissive
> mode. (Any suggestions on that appreciated as well.. "newrole -r
> sysadm_t; newrole -l s15; kill 1332" didn't work..)
>
> I'm wondering if audisp/setroubleshoot are needed for auditing to work,
> or if they are helps for X applications, in which case they aren't
> needed at all, since X doesn't run in MLS enforcing.
>
>
They are not needed for auditing to work. I am not sure setroubleshoot
would even be legal in an MLS environment since it could leak sensitive
information.
If you add a module with
policy_module(myaudit, 1.0)
gen_require(`
type audisp_t;
')
mls_socket_write_all_levels(audisp_t)
Does this solve the problem?
--
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.
prev parent reply other threads:[~2008-09-04 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 19:58 setroubleshoot problems with MLS policy in enforcing mode Robert Story
2008-09-04 13:06 ` 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=48BFDD4C.50105@redhat.com \
--to=dwalsh@redhat.com \
--cc=rstory@sparta.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.