Re: [PATCH v3 0/4] Better integrate seccomp logging and auditing

2018-05-07 Thread Paul Moore
On Sun, May 6, 2018 at 7:36 PM, Kees Cook wrote: > On Sun, May 6, 2018 at 2:31 PM, Paul Moore wrote: >> On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote: >>> Seccomp received improved logging controls in v4.14. Applications can opt >>> into >>> logging of "handled" actions (SECCOMP_RET_TRAP, S

Re: [PATCH v3 0/4] Better integrate seccomp logging and auditing

2018-05-06 Thread Kees Cook
On Sun, May 6, 2018 at 2:31 PM, Paul Moore wrote: > On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote: >> Seccomp received improved logging controls in v4.14. Applications can opt >> into >> logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE, >> SECCOMP_RET_ERRNO) using the SECCOM

Re: [PATCH v3 0/4] Better integrate seccomp logging and auditing

2018-05-06 Thread Paul Moore
On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote: > Seccomp received improved logging controls in v4.14. Applications can opt into > logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE, > SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading filters. > They can also

[PATCH v3 0/4] Better integrate seccomp logging and auditing

2018-05-03 Thread Tyler Hicks
Seccomp received improved logging controls in v4.14. Applications can opt into logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE, SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading filters. They can also debug filter matching with the new SECCOMP_RET_LOG action. A