-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: do not log encoded secrets #596
fix: do not log encoded secrets #596
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## hotfix/4.8 #596 +/- ##
=============================================
Coverage ? 90.39%
=============================================
Files ? 66
Lines ? 3989
Branches ? 454
=============================================
Hits ? 3606
Misses ? 295
Partials ? 88 ☔ View full report in Codecov by Sentry. |
27ca53e
to
f6b1f87
Compare
edcfa2b
to
19faa83
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed with Alex that this should be 4.6.1, but otherwise looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since @mattculler agrees I've gone ahead and re-targeted this at the 4.6 hotfix branch. I can celease as soon as @medubelko approves the changelog.
a387d4c
to
38d3a8c
Compare
I've rebased it on the top of |
bacee16
to
0f0fae7
Compare
Signed-off-by: Dariusz Duda <dariusz.duda@canonical.com>
0f0fae7
to
cc644d1
Compare
tox
?Encoded secrets leak in the logs of the host instance, when managed instance is about to run. If additionally subsequent process fails, value is printed again in the failure traceback.
As they're only encoded not encrypted we should take a precautions and hide those values from the user.