From: Paul Moore <paul@paul-moore.com>
To: "Boyce, Kevin P (AS)" <Kevin.Boyce@ngc.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: EXT :Fold CONFIG_AUDITSYSCALL into CONFIG_AUDIT?
Date: Tue, 24 Nov 2015 09:07:53 -0500 [thread overview]
Message-ID: <CAHC9VhRtVvX6=d7BT24EaCXL9p4hzW1bu99gQOAwtm0dPLF=sA@mail.gmail.com> (raw)
In-Reply-To: <97985b6b623c49f1bcf121e1541f268e@XCGVAG30.northgrum.com>
On Tue, Nov 24, 2015 at 8:58 AM, Boyce, Kevin P (AS)
<Kevin.Boyce@ngc.com> wrote:
> Having never looked at the code, it sounds reasonable to me. It doesn't make a lot of sense to disable syscall auditing independently.
I'd be very surprised to hear if anyone is running audit *without*
syscall auditing, but I thought I would toss the question out there on
the off chance I'm missing some critical use case.
> -----Original Message-----
> From: linux-audit-bounces@redhat.com [mailto:linux-audit-bounces@redhat.com] On Behalf Of Paul Moore
> Sent: Monday, November 23, 2015 5:43 PM
> To: linux-audit@redhat.com
> Subject: EXT :Fold CONFIG_AUDITSYSCALL into CONFIG_AUDIT?
>
> Does anyone out there build kernels with CONFIG_AUDIT=y and CONFIG_AUDITSYSCALL=n? I'm thinking of simply removing the CONFIG_AUDITSYSCALL knob and moving all that code under CONFIG_AUDIT, does anyone have any objections?
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2015-11-24 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 22:42 Fold CONFIG_AUDITSYSCALL into CONFIG_AUDIT? Paul Moore
2015-11-24 13:58 ` EXT :Fold " Boyce, Kevin P (AS)
2015-11-24 14:07 ` Paul Moore [this message]
2015-11-24 17:25 ` Boyce, Kevin P (AS)
2015-11-24 18:03 ` 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='CAHC9VhRtVvX6=d7BT24EaCXL9p4hzW1bu99gQOAwtm0dPLF=sA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=Kevin.Boyce@ngc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.