fix(security): sanitize secrets in debug logs #124
Merged
+298
−10
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.
Summary
KAPSIS_DEBUGwas enabledsanitize_secrets()function to mask sensitive values in log outputlog_cmd(),log_enter(), andlog_var()to automatically sanitize their outputChanges
scripts/lib/logging.shscripts/launch-agent.shscripts/entrypoint.shtests/test-logging.shPatterns Masked
Variables containing these keywords (case-insensitive) are now masked:
KEY,TOKEN,SECRET,PASSWORD,CREDENTIALSAUTH,BEARER,API_KEY,PRIVATEExample
Before:
After:
Test plan
sanitize_secrets()correctly masks sensitive patternsKAPSIS_DEBUG=1to verify no secrets leak🤖 Generated with Claude Code