From: Brad Willson <bwil150n@u.washington.edu>
To: selinux@tycho.nsa.gov
Cc: Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: SEL+RHEL4+Amanda, targeted policy 18, enforcing
Date: Tue, 07 Mar 2006 11:13:40 -0800 [thread overview]
Message-ID: <440DDB64.8090109@u.washington.edu> (raw)
In-Reply-To: <1141757023.19447.267.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>That's fine; you only need the avc messages from /var/log/messages then.
>If you had been running auditd, then they would have gone to audit.log
>instead, and possibly been supplemented with syscall audit records, but
>that isn't required.
>
>
>
Starting up auditd just solved another issue, thanks! I'm tailing both
/var/log/messages and /var/log/audit/audit.log to see what happens.
>Ultimately you want to resolve all of the avc messages, but possibly you
>should just start by posting the first few or the ones that seem most
>relevant to amanda itself (but try to avoid duplicates).
>
>
>
A slice at a time is fine with me. There seems to be a quantum leap
between targeted and strict.
>Note that since you are using RHEL, you should also be reporting this to
>Red Hat so that any ultimate fix can be included in a RHEL update;
>otherwise you may end up hitting the problem repeatedly. Filed a
>bugzilla there yet?
>
>
>
I've not submitted a report yet; I try to gather as much information
about a bug as I can before I send a report.
Meanwhile I wait for my SELinux book from O'Reilly...due in tomorrow!
--
Brad Willson
Sr. Computer Specialist
UW GeneTests, http://www.genetests.org
EM: bwil150n@u.washington.edu
W: 206.221.4674, C: 425.891.2732
--
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:[~2006-03-07 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 6:01 SEL+RHEL4+Amanda, targeted policy 18, enforcing Brad Willson
2006-03-07 13:18 ` Stephen Smalley
2006-03-07 17:52 ` Brad Willson
2006-03-07 18:43 ` Stephen Smalley
2006-03-07 19:13 ` Brad Willson [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=440DDB64.8090109@u.washington.edu \
--to=bwil150n@u.washington.edu \
--cc=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.