test(worker): verify child at the input caps, brk bounded by the limits

Max frame (document and base 2 MiB, drawings 6 MiB) passes through the full
sandbox; refusals just beyond give caps verdicts; RLIMIT_AS and the argument
filters still stop the verify child; seccomp traced on the max input; the two
tracked misclassifications asserted as current behaviour.
This commit is contained in:
bchanot committed 2026-11-01 21:07:23 +01:00
1 parent a6de7d6b94
commit e967ce6736
5 files changed
+385 -3

No files matched your search

+4 -3
View File
@@ -3,8 +3,9 @@
# checks it against `sandbox::ALLOWED_SYSCALLS` (review Part IV.1: "derived by strace over
# the fixture corpus at the caps on the production image, not hand-written"). Runs in the
# Alpine `test` stage of crates/worker/Dockerfile, where the musl binary that ships is built.
# The verify child (V1-2.3) shares the filter: its framed fixtures (a small sheet and the
# sheet at every cap) are traced the same way.
# The verify child (V1-2.3) shares the filter: its framed fixtures (a small sheet, the
# sheet at every cap and the input at the maximum: 2 MiB document and base, four drawings)
# are traced the same way.
#
# Exit 1 when a traced syscall is missing from the allowlist (the sandbox would kill a
# legitimate decode or verification). Syscalls the list allows but the trace never shows are
@@ -31,7 +32,7 @@ trace() {
for kind in png jpeg webp big-jpeg big-png; do
trace decode "$kind"
done
for kind in verify-clean verify-caps; do
for kind in verify-clean verify-caps verify-max; do
trace verify "$kind"
done
sort -u "$work/traced.raw" > "$work/traced.txt"