Potential fix for code scanning alert no. 5: Clear-text logging of sensitive information#6
Draft
johnteee wants to merge 1 commit into
Draft
Potential fix for code scanning alert no. 5: Clear-text logging of sensitive information#6johnteee wants to merge 1 commit into
johnteee wants to merge 1 commit into
Conversation
…nsitive information Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.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
1 participant
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.
Potential fix for https://github.com/TeaEntityLab/teaAgent/security/code-scanning/5
Best fix: keep behavior (validation + user-facing errors) but remove dynamic sensitive content from error strings returned by
_load_key_ring, so line 27 can safely print generic errors.In
teaagent/cli/_handlers/_mcp.py, update_load_key_ringerror messages that currently include{path},{exc},{kid!r}, or{active_kid!r}to static/sanitized text. This addresses both variants becauseerrorat line 27 will no longer carry tainted sensitive data. No functional flow changes are needed; only message content changes.Suggested fixes powered by Copilot Autofix. Review carefully before merging.