You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A maintainer can find which system call the worker sandbox's filter killed #27
A short section in docs/develop.md, "A grant worker died of SIGSYS", that tells a maintainer how to find the system call the worker sandbox's filter killed. Building #22 took several tries with strace wrappers before finding the two commands that work:
journalctl -k | grep type=1326 prints the kernel's audit line for each filter kill, with syscall=<number> and arch=, and needs no root. In CI the same lines come from sudo dmesg, which the workflows already print when a run fails.
strace -D -f -o <file> target/debug/countersign-gateway serve <config> traces a Gateway under the runtime test. -D matters: the runtime test stops every descendant of the Gateway, and without it that includes the tracer.
Say also how to turn the number into a name for the architecture (ausyscall <arch> <number>, or the kernel's unistd.h), and that a new entry goes in the allow-list in crates/countersign-gateway/src/worker_sandbox.rs with the reason beside it.
Acceptance criteria
docs/develop.md has the section, with both commands and why -D is needed
It says how to map a system call number to its name on x86-64 and arm64
mkdocs build --strict passes
From the retro of #22 Grant workers confine themselves under the namespace sandbox.
Activity
feat(gateway): Every grant worker confines itself before it reads any…