Re: [systemd-devel] Seccomp allow/log action

2020-07-14 Thread Lennart Poettering
On Mo, 13.07.20 10:02, Chris PeBenito (chpeb...@linux.microsoft.com) wrote: > > I think it would be more flexible to extend the error code return per > > system call, like > > SystemCallFilter=gettimeofday:LOG > > Yes, that provides much more granularity but is it necessary to support that > level

Re: [systemd-devel] Seccomp allow/log action

2020-07-13 Thread Chris PeBenito
On 7/8/20 2:31 PM, Topi Miettinen wrote: On 8.7.2020 17.47, Chris PeBenito wrote: I would like to implement a unit option that would make the seccomp action SCMP_ACT_LOG so that I can test SystemCallFilter settings without killing the services, like SELinux permissive mode. I was reading this

Re: [systemd-devel] Seccomp allow/log action

2020-07-08 Thread Topi Miettinen
On 8.7.2020 17.47, Chris PeBenito wrote: I would like to implement a unit option that would make the seccomp action SCMP_ACT_LOG so that I can test SystemCallFilter settings without killing the services, like SELinux permissive mode. I was reading this github issue about seccomp actions from l

[systemd-devel] Seccomp allow/log action

2020-07-08 Thread Chris PeBenito
I would like to implement a unit option that would make the seccomp action SCMP_ACT_LOG so that I can test SystemCallFilter settings without killing the services, like SELinux permissive mode. I was reading this github issue about seccomp actions from last year: https://github.com/systemd/syst