-
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
base: hotfix/4.6
Are you sure you want to change the base?
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 @@
## main #596 +/- ##
==========================================
- Coverage 99.28% 90.36% -8.93%
==========================================
Files 29 65 +36
Lines 1265 3976 +2711
Branches 209 456 +247
==========================================
+ Hits 1256 3593 +2337
- Misses 6 295 +289
- Partials 3 88 +85 ☔ View full report in Codecov by Sentry. |
27ca53e
to
f6b1f87
Compare
f6b1f87
to
edcfa2b
Compare
Signed-off-by: Dariusz Duda <[email protected]>
edcfa2b
to
19faa83
Compare
docs/reference/changelog.rst
Outdated
@@ -4,6 +4,16 @@ | |||
Changelog | |||
********* | |||
|
|||
4.7.0 (YYYY-MMM-DD) |
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.
Should we do this in a 4.6.1 patch release?
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.
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.