[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJYaQTB6g-wgg5TXijVm-LYs6zoUK_GsNh5+ZAF3xMtSA@mail.gmail.com>
Date: Wed, 15 Feb 2017 17:13:38 -0800
From: Kees Cook <keescook@...omium.org>
To: Tyler Hicks <tyhicks@...onical.com>
Cc: Paul Moore <paul@...l-moore.com>, Eric Paris <eparis@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>, linux-audit@...hat.com,
LKML <linux-kernel@...r.kernel.org>,
John Crispin <john@...ozen.org>,
Linux API <linux-api@...r.kernel.org>
Subject: Re: [PATCH v4 4/4] seccomp: Add tests for SECCOMP_RET_LOG
On Mon, Feb 13, 2017 at 7:55 PM, Tyler Hicks <tyhicks@...onical.com> wrote:
> Extend the kernel selftests for seccomp to test the newly added
> SECCOMP_RET_LOG action. The added tests follow the example of existing
> tests.
>
> Unfortunately, the tests are not capable of inspecting the audit log to
> verify that the syscall was logged.
It could try to read dmesg... :P But I don't need that for this patch,
though maybe add it to the test's TODO list?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists