Repository navigation
loosens constraints on web security tools - #165
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.
Loosen web-security tool constraints
Optional tools (Caido, Burp, exiftool, agent-browser, wrangler, ast-grep, waymore, pacu, fireprox, archivealchemist) no longer fail sandbox provisioning when they can't install. Only the core required tools remain fatal.
Changes
sealed-mode fast path that validates presenttools without running any installer.
severity — only ok or error). Bumped to
2.0.2.Why
Sealed and offline deployments legitimately ship without the optional tools. They shouldn't block boot or light up the health panel red.