From: Paul Moore <pmoore@redhat.com>
To: linux-audit@redhat.com
Cc: Tony Jones <tonyj@suse.de>, linux-security-module@vger.kernel.org
Subject: Re: [RFC PATCH] audit: force seccomp event logging to honor the audit_enabled flag
Date: Tue, 24 Nov 2015 13:57:35 -0500 [thread overview]
Message-ID: <2926601.ZKozHlF6o1@sifl> (raw)
In-Reply-To: <CAHC9VhSSFU_Sov+Q7fZESOnHOA6-rNOQVLahiiwOB7gfAqovBw@mail.gmail.com>
On Monday, November 23, 2015 05:35:58 PM Paul Moore wrote:
> On Mon, Nov 23, 2015 at 5:20 PM, Tony Jones <tonyj@suse.de> wrote:
> > On 11/23/2015 02:20 PM, Paul Moore wrote:
> >> Previously we were emitting seccomp audit records regardless of the
> >> audit_enabled setting, a deparature from the rest of audit. This
> >> patch makes seccomp auditing consistent with the rest of the audit
> >> record generation code in that when audit_enabled=0 nothing is logged
> >> by the audit subsystem.
> >>
> >> The bulk of this patch is moving the CONFIG_AUDIT block ahead of the
> >> CONFIG_AUDITSYSCALL block in include/linux/audit.h; the only real
> >> code change was in the audit_seccomp() definition.
> >>
> >> Reported-by: Tony Jones <tonyj@suse.de>
> >> Signed-off-by: Paul Moore <pmoore@redhat.com>
> >
> > Seems pretty much the same (functionally) as the patch I posted to audit
> > list on 10/12/2015 except that didn't hoist the entire block.
>
> Yep, I prefered to move the block as I think it should have been that
> way anyway from the start. IMHO we got to many audit Kconfig knobs
> as-is and splitting that block for just the audit_enabled flag made
> things worse.
>
> > Signed-off-by: Tony Jones <tonyj@suse.de>
I just merged this patch into audit#next, the only change is I replaced the
"Reported-by" for Tony with his sign-off.
--
paul moore
security @ redhat
prev parent reply other threads:[~2015-11-24 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 22:20 [RFC PATCH] audit: force seccomp event logging to honor the audit_enabled flag Paul Moore
2015-11-23 22:20 ` Tony Jones
2015-11-23 22:35 ` Paul Moore
2015-11-24 18:57 ` Paul Moore [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=2926601.ZKozHlF6o1@sifl \
--to=pmoore@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=tonyj@suse.de \
/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