-
Notifications
You must be signed in to change notification settings - Fork 115
Bind userauth username to the first request #1063
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
Open
yosuke-wolfssl
wants to merge
1
commit into
wolfSSL:master
Choose a base branch
from
yosuke-wolfssl:fix/f_5829
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
🔵 [Low] Same-user multi-method retry path not covered by a regression test
💡 SUGGEST
testThe new guard added in
DoUserAuthRequestintentionally allows a secondUSERAUTH_REQUESTwhen the username is unchanged (e.g. publickey probe then password, or a failed password retry). The PR description explicitly claims "Same-username multi-method retries ... are unaffected, since the username does not change," but no test asserts this positive path: every added test either changes the username (expected disconnect) or uses a single request. A latent bug that erroneously rejected a same-user second request (for example a bad size comparison) would not be caught. Adding a test that sends two same-user requests and asserts the second is accepted (notWS_INVALID_STATE_E, noMSGID_DISCONNECT) would lock in the intended behavior.Recommendation: Add a positive-path regression test for a same-username second request to protect the allowed retry behavior. Suggested: a TestSameUserSecondRequestAllowed() that issues two BuildUserAuthPasswordRequest("alice", ...) calls and asserts the second DoReceive does not disconnect and re-invokes the callback bound to alice.