-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Fix logging of key changes to be consistent #68113
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
base: 3006.x
Are you sure you want to change the base?
Fix logging of key changes to be consistent #68113
Conversation
Fixes logging of master aes and session keys changes to be correct and consistent. Also simplifies the code and reduces duplication.
@dwoz - if you aren't up for merging this before 3006.13, no worries - I can always bring it back at a later stage |
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.
Could we get a changelog and some tests?
We staged |
What does this PR do?
Fixes logging of master aes and session keys changes to be correct and consistent. This was useful when testing issues in #68085 to understand what is actually happening.
Also removes some duplication of code.
What issues does this PR fix or reference?
Debug logging for master AES and session keys was incomplete and inconsistent across AsyncAuth._authenticate() and SAuth.authenticate()
Previous Behavior
AsyncAuth._authenticate() logged both master AES and session key changes as "The master's aes key has changed".
SAuth.authenticate() didn't log anything.
New Behavior
Both functions consistently log:
The wording isn't ideal, but assuming that people may be used to those messages I didn't want to change too much.
Commits signed with SSH key?
Yes