I'll look into it. Anyway, is there any
specific reason for not providing an option to disable seccomp (or
make seccomp opt-in instead of default)?
Thanks,
Mohan R
___
systemd-devel mailing list
[email protected]
https://lists.f
call-filter=openat2
> to allow a specific syscall on top of our defaults, i.e. extend the
> allow list, or remove entries from it.
This '--system-call-filter' isn't working,
https://gist.github.com/mohan43u/6ed44eff564f10cc04c709772b02c323
Is this a
t the container inside seccomp faltered
(Seccomp: 2). But I'm not able to get the list of filtered syscalls or
I'm not able to find out why 'openat2()' is returning EPERM inside the
systemd-nspawn container.
Thanks,
Mohan R
___
systemd-d
d --user' to provide different
DBUS_SESSION_BUS_ADDRESS to the childs?
Thanks,
Mohan R
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel