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
In order to sandbox the PVF workers, we want to use seccomp to block all unneeded syscalls. We can get the list of syscalls used by the processes with the list-syscalls.rb script. However, we need a CI job to keep this list up to date.
Requirements
Add to the repo the list of syscalls detected by list-syscalls.rb.
Let's call the lists prepare-worker-syscalls and execute-worker-syscalls.
Add a CI job that:
Builds the workers with LTO (production profile) and musl: SKIP_WASM_BUILD=1 cargo build --profile production --target x86_64-unknown-linux-musl --bin polkadot-execute-worker --bin polkadot-prepare-worker.
Runs list-syscalls.rb on both workers and compares the output to prepare-worker-syscalls and execute-worker-syscalls.
Any changes should be reviewed manually. (I don't expect changes to occur often.)
The text was updated successfully, but these errors were encountered:
Background
In order to sandbox the PVF workers, we want to use seccomp to block all unneeded syscalls. We can get the list of syscalls used by the processes with the list-syscalls.rb script. However, we need a CI job to keep this list up to date.
Requirements
list-syscalls.rb
.prepare-worker-syscalls
andexecute-worker-syscalls
.SKIP_WASM_BUILD=1 cargo build --profile production --target x86_64-unknown-linux-musl --bin polkadot-execute-worker --bin polkadot-prepare-worker
.list-syscalls.rb
on both workers and compares the output toprepare-worker-syscalls
andexecute-worker-syscalls
.The text was updated successfully, but these errors were encountered: