Fix code scanning alert no. 6: Clear-text logging of sensitive information #413
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.
Fixes /~https://github.com/no-src/gofs/security/code-scanning/6
To fix the problem, we need to ensure that sensitive information, such as user passwords, is not logged in clear text. The best way to fix this issue without changing existing functionality is to modify the logging statement to exclude the password information. Instead of logging the entire
cp.Users
string, we should log only the usernames or other non-sensitive information.We will modify the
generateRandomUser
function in thecmd/gofs.go
file to log only the usernames of the generated users. This can be achieved by creating a new function that extracts and returns only the usernames from the user list.Suggested fixes powered by Copilot Autofix. Review carefully before merging.