From: Steve Grubb <sgrubb@redhat.com>
To: "John C. A. Bambenek, GCIH, CISSP" <bambenek.infosec@gmail.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Audit log file perms
Date: Wed, 21 Aug 2013 16:09:41 -0400 [thread overview]
Message-ID: <1611637.gEVO1ZgO7O@x2> (raw)
In-Reply-To: <CACDVn2PMxFS2d1Q1F-ShziQ-w81Q+8fgoAxhde9NiPRks0G4QQ@mail.gmail.com>
On Wednesday, August 21, 2013 02:34:36 PM John C. A. Bambenek, GCIH, CISSP
wrote:
> Files have right permissions but the directory itself keeps reverting to
> root:root and 700.
The audit daemon does not change permissions on the directory. Its assumed the
admin takes care of that since you would set that up once and it should be
good for a while. The audit daemon just changes the files because it creates
them and rotates them.
-Steve
> On Thursday, August 1, 2013, Steve Grubb wrote:
> > On Thursday, August 01, 2013 12:34:20 PM John Bambenek wrote:
> > > What controls that?
> >
> > The audit daemon.
> >
> > > I have noticed /var/log/audit directory changes to a
> > > default setting quickly and file rotation resets it as well.
> >
> > It defaults to 0600 unless you have set something for log_group and in
> > that
> > case you get 0640. Rotation is done using the rename syscall, so no
> > permissions should be changing. Logs are created as 0640 root, root. But
> > get
> > modified as the audit daemon gets more of its configuration parsed.
> >
> > -Steve
> >
> > --
> > Linux-audit mailing list
> > Linux-audit@redhat.com <javascript:;>
> > https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2013-08-21 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 17:34 Audit log file perms John Bambenek
2013-08-01 17:54 ` Steve Grubb
2013-08-21 19:34 ` John C. A. Bambenek, GCIH, CISSP
2013-08-21 20:09 ` 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=1611637.gEVO1ZgO7O@x2 \
--to=sgrubb@redhat.com \
--cc=bambenek.infosec@gmail.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