From: Daniel J Walsh <dwalsh@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: Audit2allow/audit2why patch for policycoreutils.
Date: Tue, 18 Mar 2008 11:27:06 -0400 [thread overview]
Message-ID: <47DFDF4A.8090006@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Reveals dontaudit rules in policy.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkff30kACgkQrlYvE4MpobP0IgCfTxNojL6yGB6t26Nl+aERmQc4
pJUAoNlJHmee/Q++U18HG2ty5UcECkte
=qpCx
-----END PGP SIGNATURE-----
[-- Attachment #2: audit2why.patch --]
[-- Type: text/plain, Size: 1046 bytes --]
--- nsapolicycoreutils/audit2allow/audit2allow 2008-01-28 16:52:25.000000000 -0500
+++ policycoreutils-2.0.44/audit2allow/audit2allow 2008-03-18 11:22:52.000000000 -0400
@@ -247,6 +247,11 @@
print "\t\tPossible mismatch between this policy and the one under which the audit message was generated.\n"
print "\t\tPossible mismatch between current in-memory boolean settings vs. permanent ones.\n"
continue
+ if rc == audit2why.DONTAUDIT:
+ print "\t\tUnknown - should be dontaudit'd by active policy\n",
+ print "\t\tPossible mismatch between this policy and the one under which the audit message was generated.\n"
+ print "\t\tPossible mismatch between current in-memory boolean settings vs. permanent ones.\n"
+ continue
if rc == audit2why.BOOLEAN:
if len(bools) > 1:
print "\tOne of the following booleans was set incorrectly."
[-- Attachment #3: audit2why.patch.sig --]
[-- Type: application/octet-stream, Size: 72 bytes --]
next reply other threads:[~2008-03-18 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 15:27 Daniel J Walsh [this message]
2008-03-18 20:38 ` Audit2allow/audit2why patch for policycoreutils 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=47DFDF4A.8090006@redhat.com \
--to=dwalsh@redhat.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.