From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Moore Subject: Re: [PATCH] audit: Don't spam logs with SECCOMP_KILL/RET_ERRNO by default Date: Mon, 11 Apr 2016 21:17:46 -0400 Message-ID: <1688459.VTSZtqjx8i@sifl> References: <1460348008-27076-1-git-send-email-andi@firstfloor.org> <1460390286.3268.36.camel@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <1460390286.3268.36.camel@redhat.com> Sender: linux-kernel-owner@vger.kernel.org To: Eric Paris Cc: Andi Kleen , linux-kernel@vger.kernel.org, Andi Kleen , linux-audit@redhat.com List-Id: linux-audit@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