From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <pmoore@redhat.com>, eparis@parisplace.org
Cc: Richard Guy Briggs <rgb@redhat.com>, linux-audit@redhat.com
Subject: Re: [PATCH] audit: convert status version to a feature bitmap
Date: Mon, 17 Nov 2014 12:23:57 -0500 [thread overview]
Message-ID: <13752367.yccC5JN0ln@x2> (raw)
In-Reply-To: <3782801.lIH1fB4Omg@sifl>
On Monday, November 17, 2014 11:09:08 AM Paul Moore wrote:
> On Friday, November 14, 2014 10:32:51 PM Richard Guy Briggs wrote:
> > On 14/11/13, Steve Grubb wrote:
> > > On Thursday, November 13, 2014 08:08:52 PM Richard Guy Briggs wrote:
> > > The audit 2.4.1 package has been pushed to everything from F20 ->
> > > rawhide.
> > > If you don't see any problems, then its safe. But check carefully around
> > > the things that you did change. Right now, we only are caring about only
> > > one kernel feature, --loginuid-immutable. Check that it still works,
> > > auditctl -s.
> >
> > Here's my output, which I assume looks sane:
Yeah, but how do we know its really selecting the right feature?
> > [root@f20 ~]# rpm -q audit
> > audit-2.4.1-1.fc20.x86_64
> > [root@f20 ~]# auditctl -s
> > enabled 1
> > flag 1
> > pid 307
> > rate_limit 0
> > backlog_limit 320
> > lost 0
> > backlog 0
> > backlog_wait_time 60000
> > loginuid_immutable 0 unlocked
>
> Looks like good output to me, Steve?
I would like it better if the following was tested as root:
auditctl -s
echo "1" > /proc/self/loginuid
auditctl --loginuid-immutable
auditctl -s
echo "2" > /proc/self/loginuid
This was we know that the feature is correctly reported, selected, and
working.
-Steve
next prev parent reply other threads:[~2014-11-17 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 20:29 [PATCH] audit: convert status version to a feature bitmap Richard Guy Briggs
2014-11-13 20:38 ` Joe Perches
2014-11-13 22:00 ` Paul Moore
2014-11-14 1:01 ` Richard Guy Briggs
2014-11-13 22:12 ` Paul Moore
2014-11-14 1:08 ` Richard Guy Briggs
2014-11-14 2:51 ` Steve Grubb
2014-11-15 3:32 ` Richard Guy Briggs
2014-11-17 16:09 ` Paul Moore
2014-11-17 17:23 ` Steve Grubb [this message]
2014-11-17 18:08 ` Richard Guy Briggs
2014-11-17 18:11 ` Steve Grubb
2014-11-17 18:16 ` Richard Guy Briggs
2014-11-17 19:48 ` Paul Moore
2014-11-17 20:51 ` Richard Guy Briggs
2014-11-17 21:59 ` Paul Moore
2014-11-14 13:32 ` Paul Moore
2014-11-14 13:32 ` Paul Moore
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=13752367.yccC5JN0ln@x2 \
--to=sgrubb@redhat.com \
--cc=eparis@parisplace.org \
--cc=linux-audit@redhat.com \
--cc=pmoore@redhat.com \
--cc=rgb@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 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.