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

2017-08-10 Thread Tyler Hicks
On 08/04/2017 05:24 PM, Tyler Hicks wrote: > On 08/03/2017 11:33 AM, Kees Cook wrote: >> On Fri, Jul 28, 2017 at 1:55 PM, Tyler Hicks wrote: >>> Adminstrators can write to this sysctl to set the seccomp actions that >>> are allowed to be logged. Any actions not found in this sysctl will not >>> be

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

2017-08-07 Thread Tyler Hicks
On 2017-08-04 17:24:00, Tyler Hicks wrote: > On 08/03/2017 11:33 AM, Kees Cook wrote: > > On Fri, Jul 28, 2017 at 1:55 PM, Tyler Hicks wrote: > >> Adminstrators can write to this sysctl to set the seccomp actions that > >> are allowed to be logged. Any actions not found in this sysctl will not > >

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

2017-08-04 Thread Tyler Hicks
On 08/03/2017 11:33 AM, Kees Cook wrote: > On Fri, Jul 28, 2017 at 1:55 PM, Tyler Hicks wrote: >> Adminstrators can write to this sysctl to set the seccomp actions that >> are allowed to be logged. Any actions not found in this sysctl will not >> be logged. >> >> For example, all SECCOMP_RET_KILL,

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

2017-08-03 Thread Kees Cook
On Fri, Jul 28, 2017 at 1:55 PM, Tyler Hicks wrote: > Adminstrators can write to this sysctl to set the seccomp actions that > are allowed to be logged. Any actions not found in this sysctl will not > be logged. > > For example, all SECCOMP_RET_KILL, SECCOMP_RET_TRAP, and > SECCOMP_RET_ERRNO actio