From: Steve Grubb <sgrubb@redhat.com>
To: Enzo Matsumiya <ematsumiya@suse.de>
Cc: linux-audit@redhat.com
Subject: Re: [RFC] audit.spec: create audit group for log read access
Date: Wed, 20 Jan 2021 18:15:10 -0500 [thread overview]
Message-ID: <8724290.CDJkKcVGEf@x2> (raw)
In-Reply-To: <20210120213911.32v27lqeqhrdm53i@hyori>
On Wednesday, January 20, 2021 4:39:11 PM EST Enzo Matsumiya wrote:
> >I consider the audit.spec file to be an example to help others with
> >packaging. But I'm not entirely sure if it's 100% in sync with Fedora
> >since they make arbitrary policy changes like removing gcc and make from
> >the build root which then causes specfile updates. If you want to submit
> >a patch, feel free. I would apply it as an example to others.
>
> Thanks. We also have some modifications to the specfile.
>
> So what I'm getting from your reply is it's up to the OS vendor to provide,
> or not, such modification -- i.e. it's more of a general OS problem than
> audit's problem. Is that correct?
I consider it to be an end user choice. Because if you set the log_group, you
may need to do a chgrp command to get your logs in order. And I don't know
who should get access. Would it be wheel or a special audit-view group? To
me, it just seems like any choice I make may not work for everyone.
But you're welcome to send a patch if you want.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2021-01-20 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 17:52 [RFC] audit.spec: create audit group for log read access Enzo Matsumiya
2021-01-20 18:16 ` Steve Grubb
2021-01-20 21:39 ` Enzo Matsumiya
2021-01-20 23:15 ` 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=8724290.CDJkKcVGEf@x2 \
--to=sgrubb@redhat.com \
--cc=ematsumiya@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).