From: Paul Moore <paul@paul-moore.com>
To: Eric Paris <eparis@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
linux-audit@redhat.com
Subject: Re: [PATCH] audit: Don't spam logs with SECCOMP_KILL/RET_ERRNO by default
Date: Mon, 11 Apr 2016 21:17:46 -0400 [thread overview]
Message-ID: <1688459.VTSZtqjx8i@sifl> (raw)
In-Reply-To: <1460390286.3268.36.camel@redhat.com>
On Monday, April 11, 2016 10:58:06 AM Eric Paris wrote:
> I'm all for a way to shut up unsolicited audit messages, especially
> seccomp with errno or trap. I think it would be best to default 'KILL'
> to on and everything else to off. I'm no so sure a sysctl is the right
> way though. Enabling more forms of 'seccomp audit' should really be a
> part of the audit policy.
The seccomp events are very useful for people who are working with seccomp
filters and I want to ensure that we have the ability to emit these events
regardless of if audit is enabled, or even compiled into the kernel using
dmesg/syslog as we do today with other auditable events, e.g. SELinux.
Because of this desire to log regardless of audit, I figured a sysctl tunable
made more sense than an audit based filter. As I mentioned previously, I'm
not completely sold on the sysctl based solution, but it is the best solution
that I can think of at the moment. Alternatives are welcome.
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2016-04-12 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460348008-27076-1-git-send-email-andi@firstfloor.org>
2016-04-11 13:30 ` [PATCH] audit: Don't spam logs with SECCOMP_KILL/RET_ERRNO by default Paul Moore
2016-04-11 15:58 ` Eric Paris
2016-04-11 21:55 ` Andi Kleen
2016-04-12 1:17 ` 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=1688459.VTSZtqjx8i@sifl \
--to=paul@paul-moore.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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