From: Andi Kleen <andi@firstfloor.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Andi Kleen <ak@linux.intel.com>, Andi Kleen <andi@firstfloor.org>,
Eric Paris <eparis@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Don't audit SECCOMP_KILL/RET_ERRNO when syscall auditing is disabled
Date: Sun, 10 Apr 2016 21:07:44 -0700 [thread overview]
Message-ID: <20160411040744.GH9407@two.firstfloor.org> (raw)
In-Reply-To: <CAHC9VhSBQu6_Ri4CFew6YBKHJ1Z7Fb091rDpiOb3_53dUuoWdw@mail.gmail.com>
On Sun, Apr 10, 2016 at 10:30:10PM -0400, Paul Moore wrote:
> On Sun, Apr 10, 2016 at 6:31 PM, Andi Kleen <ak@linux.intel.com> wrote:
> > On Sun, Apr 10, 2016 at 06:17:53PM -0400, Paul Moore wrote:
> >> On Sat, Apr 9, 2016 at 10:41 PM, Andi Kleen <andi@firstfloor.org> wrote:
> >> >> What kernel version are you using? I believe we fixed that in Linux
> >> >> 4.5 with the following:
> >> >
> >> > This is 4.6-rc2.
> >> >>
> >> >> commit 96368701e1c89057bbf39222e965161c68a85b4b
> >> >> From: Paul Moore <pmoore@redhat.com>
> >> >> Date: Wed, 13 Jan 2016 10:18:55 -0400 (09:18 -0500)
> >> >>
> >> >> audit: force seccomp event logging to honor the audit_enabled flag
> >> >
> >> > No you didn't fix it because audit_enabled is always enabled by systemd
> >> > for user space auditing, see the original description of my patch.
> >>
> >> [NOTE: adding the audit list to the CC line]
> >
> > This mailing list is marked subscriber only in MAINTAINERS so I
> > intentionally didn't add it. It's unlikely that my emails
> > will make it through.
>
> Steve Grubb checks it on a regular basis and approves anything
> remotely audit related. Please make use of it in the future; it's
> listed in MAINTAINERS for a reason.
Nothing has appeared by now. A mailing list that does not allow
real time discussion is fairly useless.
Dropped again.
> >> If you are interested, I started tracking this issue at the link below:
> >>
> >> * https://github.com/linux-audit/audit-kernel/issues/13
> >
> > Making it a sysctl is fine for me as long as it is disabled by default
> > so that user space doesn't need to be modified to make seccomp
> > stop spamming.
> >
> > Audit should always be opt-in, not opt-out.
>
> From my perspective, you, or rather systemd in your case, is opting in
> by enabling audit.
It wants an audit channel, but not random kernel subsystems
unconditionally spamming the logs. If it wanted the later it would
set audit rules.
>
> > However I think making it conditional on syscall auditing like
> > in my patch is equivalent and much simpler.
> >
> > If you really insist on the sysctl I can send patch.
>
> As I said earlier, I haven't given this a lot of thought as of yet,
> but so far I like the sysctl approach much more than the patch you
> sent earlier.
Ok I'm sending an updated patch.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2016-04-11 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 15:07 [PATCH] Don't audit SECCOMP_KILL/RET_ERRNO when syscall auditing is disabled Andi Kleen
2016-04-10 0:56 ` Paul Moore
2016-04-10 2:41 ` Andi Kleen
2016-04-10 22:17 ` Paul Moore
2016-04-10 22:17 ` Paul Moore
2016-04-10 22:31 ` Andi Kleen
2016-04-11 2:30 ` Paul Moore
2016-04-11 4:07 ` Andi Kleen [this message]
2016-04-11 13:23 ` Paul Moore
2016-04-11 13:23 ` Paul Moore
2016-04-12 20:34 ` Richard Guy Briggs
2016-04-12 20:34 ` Richard Guy Briggs
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=20160411040744.GH9407@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.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.