Prevent Leaking Passwords to the Log [master] #128
Merged
+8
−2
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.
Target Branch
This is for master, i.e. Factory, Tumbleweed and the Agama images.
A backport to SLE-15-SP5 and -SP6 will follow.
Bugzilla
https://bugzilla.suse.com/show_bug.cgi?id=1225432
Problem
Passwords may be leaked to the log.
Cause
When the configuration is written to file, it is also logged completely to the y2log. This includes any passwords that the user entered when configuring iSCSI.
Unfortunately, the config class is just a very thin wrapper around an array of hashes, not a real class with dedicated fields, so we cannot use the
secret_attr
method that we use in other places.Fix
Don't log the complete configuration, only the fact that is was written.
The log format is unwieldy and very hard to read for a human anyway, so it's not very useful to log it in the first place.
Related Branches