From: Stephen Smalley <sds@tycho.nsa.gov>
To: Xavier Toth <txtoth@gmail.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: odd policy behavior
Date: Tue, 03 Feb 2009 11:38:02 -0500 [thread overview]
Message-ID: <1233679082.14235.21.camel@localhost.localdomain> (raw)
In-Reply-To: <cadfc0e40902030828v41f836eag84d5aaa0fa7bb899@mail.gmail.com>
On Tue, 2009-02-03 at 10:28 -0600, Xavier Toth wrote:
> I have an app that wasn't working in enforcing but there are no AVCs.
> So I did 'semodule -DB' to see if there were any dontaudit denials and
> restarted the app. The problem is that the app then ran fine. So I
> tried load_policy which had no affect and 'semodule -B' which makes it
> work. Any ideas what could be happening? I've verified with 'semodule
> --list' that the module is loaded prior to doing the 'semodule -B'.
- How was the app failing?
- Did you try running the app in permissive as well?
- Is this reproducible at all or are you unable to reproduce the
application failure now under any conditions?
- Did the app create/use any transient resources (temporary files,
system v ipc objects, etc) that could have prevented it from succeeding
on subsequent execution if they weren't properly cleaned up on prior
exit?
--
Stephen Smalley
National Security Agency
--
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:[~2009-02-03 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 16:28 odd policy behavior Xavier Toth
2009-02-03 16:38 ` Stephen Smalley [this message]
2009-02-03 19:59 ` Xavier Toth
2009-02-03 21:28 ` Stephen Smalley
2009-02-03 21:49 ` Xavier Toth
2009-02-03 22:31 ` Xavier Toth
2009-02-04 13:55 ` Stephen Smalley
2009-02-04 16:12 ` Daniel J Walsh
2009-02-04 16:14 ` Stephen Smalley
2009-02-04 16:22 ` Daniel J Walsh
2009-02-04 17:11 ` Joe Nall
2009-02-04 19:28 ` James W. Hoeft
2009-02-09 16:07 ` chanson
2009-02-04 16:23 ` Daniel J Walsh
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=1233679082.14235.21.camel@localhost.localdomain \
--to=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=txtoth@gmail.com \
/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.