mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: Paul Moore <paul@paul-moore.com>, Eric Paris <eparis@redhat.com>,
	Kees Cook <keescook@chromium.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] Improved seccomp logging
Date: Fri,  3 Feb 2017 05:37:38 +0000	[thread overview]
Message-ID: <1486100262-32391-1-git-send-email-tyhicks@canonical.com> (raw)

This patch set is the second revision of the following two previously
submitted patch sets:

http://lkml.kernel.org/r/1483375990-14948-1-git-send-email-tyhicks@canonical.com
http://lkml.kernel.org/r/1483377999-15019-2-git-send-email-tyhicks@canonical.com

The patch set aims to address some known deficiencies in seccomp's current
logging capabilities:

  1. Inability to log all filter actions.
  2. Inability to selectively enable filtering; e.g. devs want noisy logging,
     users want relative quiet.
  3. Consistent behavior with audit enabled and disabled.
  4. Inability to easily develop a filter due to the lack of a
     permissive/complain mode.

The first three items were outlined by Paul Moore and are issues that I agree
with. The last one is one that I'm particularly interested in.

I deviated a little from the plan that he laid out to address the third issue.
Looking back at Paul's feedback, he wanted a way to log seccomp actions even
when the audit subsystem is disabled at build time. I felt like the bigger
problem is that, while it is common for kernels to be built with audit support,
it is far less common to actually have auditd running. Therefore, my approach
was to improve the situation when kernel audit support is enabled at build time
but audit_enabled is false at runtime. The audit subsystem forwards messages
onto syslog in that situation.

Tyler

             reply	other threads:[~2017-02-03  5:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03  5:37 Tyler Hicks [this message]
2017-02-03  5:37 ` [PATCH v2 1/4] seccomp: Add sysctl to display available actions Tyler Hicks
2017-02-08  0:03   ` Kees Cook
2017-02-08  0:25     ` Tyler Hicks
2017-02-08  0:43       ` Kees Cook
2017-02-14  0:25         ` Tyler Hicks
2017-02-14  0:26           ` Kees Cook
2017-02-03  5:37 ` [PATCH v2 2/4] seccomp: Add sysctl to configure actions that should be logged Tyler Hicks
2017-02-08  0:24   ` Kees Cook
2017-02-10 23:56     ` Tyler Hicks
2017-02-11  0:05       ` Kees Cook
2017-02-03  5:37 ` [PATCH v2 3/4] seccomp: Create an action to log before allowing Tyler Hicks
2017-02-08  0:33   ` Kees Cook
2017-02-09 21:49     ` Kees Cook
2017-02-11  0:01     ` Tyler Hicks
2017-02-11  0:08       ` Kees Cook
2017-02-11  0:15         ` Tyler Hicks
2017-02-03  5:37 ` [PATCH v2 4/4] seccomp: Add tests for SECCOMP_RET_LOG Tyler Hicks
2017-02-08  0:39   ` Kees Cook
2017-02-07 23:58 ` [PATCH v2 0/4] Improved seccomp logging Kees Cook

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=1486100262-32391-1-git-send-email-tyhicks@canonical.com \
    --to=tyhicks@canonical.com \
    --cc=eparis@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=paul@paul-moore.com \
    --cc=wad@chromium.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

all inboxes | Powered by JetHome®