Re: [PATCH v6 3/6] seccomp: Sysctl to configure actions that are allowed to be logged

From
Kees Cook <hidden>
Date
2017-08-11 19:35:42
Also in
lkml
Reply to
Tyler Hicks, 2017-08-11
On Fri, Aug 11, 2017 at 12:33 PM, Tyler Hicks [off-list ref] wrote:
On 08/11/2017 02:17 PM, Kees Cook wrote:
quoted
One thought here: should "kill" be always forced on during a write?
This flag effectively cannot be disabled, so listing it (or not) in
the sysctl may be confusing...
"kill" can be silenced in the current implementation. Lets hammer out
whether or not that's the right thing to do and then we can discuss the
sysctl behavior on write. I don't personally have any concerns about an
admin being able to silence RET_KILL logs but let me know if you are
against it.
Oh right, this is fine. Yeah, as long as the default is to log it
(which it is) I'm fine. Thanks!

-Kees

-- 
Kees Cook
Pixel Security
Thread (11 messages) 11 messages, 2 authors, last reply 2017-08-11
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help