Repository navigation
Disable signal-triggered Inspector in sandbox runners - #31
Merged
Merged
Conversation
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.
Same-user tool processes can signal the credential-holding Node runner to activate Inspector, bypassing the protection provided by its execute-only binary. Launch the runner with
--disable-sigusr1through a sharedas-runner.sh --nodepath used by investigations and verification probes.The installer requires Node >=22.19 with actual flag support. Runtime verification sends a same-user signal and checks that Inspector remains inactive, alongside the existing
/procisolation check. Unsupported runtimes and launches that strip the flag fail verification.Validation:
inspectorActive: truebefore the fix and returnsfalseafterward.git diff --checkpassed.Rollout requires a successful snapshot refresh; deploying services alone does not update scripts already captured in snapshots. Live Render identity and loopback behavior were not exercised locally.
Fixes #21.