From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Filtering audit events
Date: Wed, 02 Sep 2015 19:31:04 -0400 [thread overview]
Message-ID: <4775624.T7pvS5t0tS@x2> (raw)
In-Reply-To: <84a967ab2e861435cc1d0c3553aef15f.squirrel@webmail.umbc.edu>
On Monday, August 31, 2015 09:58:42 AM rshaw1@umbc.edu wrote:
> > If you use the -i argument to ausearch, it becomes more clear what the
> > issue is. The problem is that the program is opening the file for read and
> > write, but the permissions are just for group read. If that file were
> > 0660, then you would not get this audit event.
>
> Hrm. The process is running as the root user, though. It's going over
> the whole filesystem (for backups).
But look at all the uids it has:
auid=7538 uid=0 gid=9002 euid=4990 suid=4990 fsuid=4990
egid=9002 sgid=9002 fsgid=9002
I'm betting it;s a setuid program and is being prevented by various checks.
Its effective uid is 4990, its fsuid is 4990. If changing the permissions is
acceptable and fixes its, that what I'd do.
-Steve
prev parent reply other threads:[~2015-09-02 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 12:18 Filtering audit events rshaw1
2015-08-31 13:22 ` Steven Grubb
2015-08-31 13:58 ` rshaw1
2015-09-02 23:31 ` Steve Grubb [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=4775624.T7pvS5t0tS@x2 \
--to=sgrubb@redhat.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