From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: eparis@parisplace.org, linux-audit@redhat.com
Subject: Re: [PATCH] audit: convert status version to a feature bitmap
Date: Mon, 17 Nov 2014 13:11:30 -0500 [thread overview]
Message-ID: <29507580.Ai7i68Ft5T@x2> (raw)
In-Reply-To: <20141117180839.GA9526@madcap2.tricolour.ca>
On Monday, November 17, 2014 01:08:39 PM Richard Guy Briggs wrote:
> > > 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.
>
> This looks sane:
Thanks for testing this.
> [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
> [root@f20 ~]# echo "1" > /proc/self/loginuid
> [root@f20 ~]# auditctl --loginuid-immutable
> [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 1 locked
> [root@f20 ~]# echo "2" > /proc/self/loginuid
> -bash: echo: write error: Operation not permitted
OK. Looks good to me, too.
-Steve
next prev parent reply other threads:[~2014-11-17 18:11 UTC|newest]
Thread overview: 17+ 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
2014-11-17 18:08 ` Richard Guy Briggs
2014-11-17 18:11 ` Steve Grubb [this message]
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
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=29507580.Ai7i68Ft5T@x2 \
--to=sgrubb@redhat.com \
--cc=eparis@parisplace.org \
--cc=linux-audit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox