From: Darrel Goeddel <dgoeddel@trustedcs.com>
To: Chad Hanson <chanson@trustedcs.com>
Cc: linux-audit@redhat.com
Subject: Re: audit 1.2.2 released
Date: Fri, 26 May 2006 11:05:32 -0500 [thread overview]
Message-ID: <4477274C.8020100@trustedcs.com> (raw)
In-Reply-To: <36282A1733C57546BE392885C061859201264DAD@chaos.tcs.tcs-sec.com>
Chad Hanson wrote:
> Comments below...
>
>
>>I've been running mostly on an i686 (Intel) with the .27 kernel and
>>1.2.2 tools with the MLS policy. I've tested this on an x86_64 (AMD
>>opteron) and see this problem too. However, this problem does
>>NOT exist
>>when using targeted policy, so it is most likely an MLS SELinux issue.
>>My MLS policy is 2.2.42
>>
>>
>>>Can you describe more about your configuration and provide exact steps
>>>to reproduce the problem?
>>
>>1) Reboot your system (so you've a clean slate)
>>2) Login (tty or pty, doesn't matter, I've done both)
>>3) auditctl -l
>>Error sending rule list request (Operation not permitted)
>>4) auditctl -l
>>No rules (or whatever you expect to see)
>
>
> Are you running enforcing or permissive?
>
> I only see this behavior on the LSPP kernels (including 28) after
> transitioning to permissive mode, but not on the FC5 2.6.15 2054 kernel
> running MLS with the same procedures.
>
> Also, I don't see this behavior the same way. I can reboot, login, newrole
> to auditadm_r and run auditctl -l correctly everytime.
>
> The problem behavior I see is as follows below
>
> 1) newrole to secadm_r
> 2) auditctl -l -- denied as expected.
> 3) setenforce 0
> 4) auditctl -l -- denied (WRONG)
> 5) auditctl -l -- works correctly (can repeat as many times as desired)
> 6) setenforce 1 -- everything is back to normal
>
> repeat from #3 to see problems again
I can reproduce Chad's behavior on an up-to-date rawhide box (currently using
kernel 2.6.16-1.2218_FC6). If I then boot to the latest published FC5 kernel
(2.6.16-1.2122_FC5) on that machine, I do not see the problem. So... I'll
see if I can spot any changes between the two source trees that would cause
the problem. I'll also try building the working FC5 kernel with the rawhide
toolchain, and possibly building the FC6 kernel with a reduced set of patches
if it comes down to that. Does this information spark any other ideas?
--
Darrel
next prev parent reply other threads:[~2006-05-26 16:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 15:50 audit 1.2.2 released Chad Hanson
2006-05-26 16:05 ` Darrel Goeddel [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 21:26 Steve Grubb
2006-05-15 19:57 ` Michael C Thompson
2006-05-15 20:04 ` Steve Grubb
2006-05-15 20:14 ` Michael C Thompson
2006-05-16 14:53 ` Michael C Thompson
2006-05-16 15:23 ` Steve Grubb
2006-05-16 16:08 ` Michael C Thompson
2006-05-16 16:28 ` Steve Grubb
2006-05-16 15:34 ` Steve Grubb
2006-05-16 15:53 ` Linda Knippers
2006-05-16 17:23 ` Steve Grubb
2006-05-16 20:38 ` Michael C Thompson
2006-05-16 21:49 ` Steve Grubb
2006-05-16 22:31 ` Valdis.Kletnieks
2006-05-17 10:25 ` Steve Grubb
2006-05-22 17:31 ` Steve Grubb
2006-05-22 19:15 ` Xin Zhao
2006-05-22 19:24 ` Steve Grubb
2006-05-22 19:37 ` Xin Zhao
2006-05-22 19:47 ` Steve Grubb
2006-05-22 20:15 ` Xin Zhao
2006-05-23 6:56 ` Amy Griffis
2006-05-23 3:43 ` Xin Zhao
2006-05-23 15:11 ` Steve Grubb
2006-05-23 16:24 ` Michael C Thompson
2006-05-23 22:20 ` Michael C Thompson
2006-05-23 23:05 ` Linda Knippers
2006-05-24 19:44 ` Michael C Thompson
2006-05-24 20:58 ` James Antill
2006-05-25 13:48 ` Michael C Thompson
2006-05-25 15:16 ` James Antill
2006-05-25 15:22 ` Michael C Thompson
2006-05-25 15:40 ` James Antill
2006-05-24 13:04 ` Steve Grubb
2006-05-24 20:30 ` Michael C Thompson
2006-05-17 15:32 ` Michael C Thompson
2006-05-17 15:45 ` Michael C Thompson
2006-05-17 21:12 ` Michael C Thompson
2006-05-17 21:23 ` Steve Grubb
2006-05-17 21:43 ` Michael C Thompson
2006-05-17 21:55 ` Steve Grubb
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=4477274C.8020100@trustedcs.com \
--to=dgoeddel@trustedcs.com \
--cc=chanson@trustedcs.com \
--cc=linux-audit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox