891241e7e7
This syncs the seccomp profile with changes made to containerd's default
profile in [1].
The original containerd issue and PR mention:
> Security experts generally believe io_uring to be unsafe. In fact
> Google ChromeOS and Android have turned it off, plus all Google
> production servers turn it off. Based on the blog published by Google
> below it seems like a bunch of vulnerabilities related to io_uring can
> be exploited to breakout of the container.
>
> [2]
>
> Other security reaserchers also hold this opinion: see [3] for a
> blackhat presentation on io_uring exploits.
For the record, these syscalls were added to the allowlist in [4].
[1]:
|
||
|---|---|---|
| .. | ||
| fixtures | ||
| default.json | ||
| default_linux.go | ||
| generate.go | ||
| kernel_linux.go | ||
| kernel_linux_test.go | ||
| seccomp.go | ||
| seccomp_linux.go | ||
| seccomp_test.go | ||