alois31
e7188e211a
Unfortunately, io_uring is totally opaque to seccomp, and while currently there
are no dangerous operations implemented, there is no guarantee that it remains
this way. This means that io_uring should be blocked entirely to ensure that
the sandbox is future-proof. This has not been observed to cause issues in
practice.
Change-Id:
|
||
---|---|---|
.. | ||
ca-fd-leak | ||
containers | ||
coredumps | ||
fetch-git | ||
io_uring | ||
no-new-privileges | ||
setuid | ||
authorization.nix | ||
broken-userns.nix | ||
default.nix | ||
github-flakes.nix | ||
nix-copy-closure.nix | ||
nix-copy.nix | ||
nix-upgrade-nix.nix | ||
nss-preload.nix | ||
remote-builds-ssh-ng.nix | ||
remote-builds.nix | ||
sourcehut-flakes.nix | ||
symlink-resolvconf.nix | ||
tarball-flakes.nix | ||
util.nix |