pam/gdm: Keep debugging all the events, sanitizing them if needed #565
+53
−9
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.
Instead of hiding the content authentication data completely, show the
whole challenge when
pam_gdm_debug
build tag is used, or when intesting mode.
Otherwise, just show a sanitized challenge so that we don't miss the
fact that the event has happened.
In the same way, keep the conversation debugging alive so that we don't miss pieces of what we got from GDM if the content is relevant.
To sanitize the JSON I preferred to go wild and just replace the content, since it's still something happening only when debugging only, so not really something in production code.
Fixes: ca47562, 40fa85d