research(fspy): evaluate SIGSYS interception - #581
Draft
wan9chi wants to merge 25 commits into
Draft
Conversation
Co-authored-by: GPT-5 Codex <codex@openai.com>
fspy benchmarklinuxmacoswindows |
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Co-authored-by: GPT-5.6 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
Co-authored-by: GPT-5 Codex <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Motivation
fspy currently chooses LD_PRELOAD for dynamic libc executables and seccomp user notification for static or non-libc executables. That leaves direct syscalls invisible in dynamic processes and makes static tracing expensive or unavailable when another seccomp listener already exists.
This draft records feasibility research for an in-process
SECCOMP_RET_TRAPbackend. It includes controlled prototypes for SIGSYS interception, signal virtualization, temporary post-exec ptrace injection, a static-host/userland-loader fallback, frontend compatibility including esbuild 0.28.1 and Vitest browser mode, and a freestanding Rust handler blob with a lock-free fixed-capacity allocator.Scope
This is research code, not a production backend. The current ptrace bridge supports default Vitest browser mode but not Playwright
chromiumSandbox: true; Chromium loses its namespace-zygote boot handshake at that exec boundary. The decision memo recommends selecting the static-host loader before that exec. Remaining production work includes complete per-thread signal virtualization, lossless async-signal-safe event recording, mapping protection, native AArch64 execution of the Rust artifact, and validation of sandboxed Chromium through the userland-loader fallback.