Skip to content
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

ssh: use the correct token from the client #176

Closed
wants to merge 1 commit into from

Conversation

bodgit
Copy link
Contributor

@bodgit bodgit commented Jan 25, 2021

This fixes the case where AcceptSecContext is always called with the
first token sent by the client instead of the most recently sent one.
Previously, despite being being read from the client and
unmarshalled, it was never actually used.

Fixes golang/go#43875

This fixes the case where AcceptSecContext is always called with the
first token sent by the client instead of the most recently sent one.

Fixes golang/go#43875
@google-cla google-cla bot added the cla: yes label Jan 25, 2021
@bodgit bodgit changed the title Use the correct token from the client ssh: Use the correct token from the client Jan 25, 2021
@gopherbot
Copy link
Contributor

This PR (HEAD: 0d58e4d) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/crypto/+/286252 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@bodgit
Copy link
Contributor Author

bodgit commented Aug 7, 2023

Amazing that after two and a half years, this PR hasn't needed any rebasing and yet remains open.

@FiloSottile FiloSottile changed the title ssh: Use the correct token from the client ssh: use the correct token from the client Sep 19, 2023
gopherbot pushed a commit that referenced this pull request Nov 11, 2023
This fixes the case where AcceptSecContext is always called with the
first token sent by the client instead of the most recently sent one.
Previously, despite being being read from the client and unmarshalled,
it was never actually used.

Fixes golang/go#43875

Change-Id: I1967d9a107af03d6778a9437b48e785d61710ee5
GitHub-Last-Rev: 0d58e4d
GitHub-Pull-Request: #176
Reviewed-on: https://go-review.googlesource.com/c/crypto/+/286252
Run-TryBot: Filippo Valsorda <filippo@golang.org>
Auto-Submit: Filippo Valsorda <filippo@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Matthew Dempsky <mdempsky@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Run-TryBot: Nicola Murino <nicola.murino@gmail.com>
Reviewed-by: Nicola Murino <nicola.murino@gmail.com>
Reviewed-by: Filippo Valsorda <filippo@golang.org>
Reviewed-by: Than McIntosh <thanm@google.com>
@bodgit
Copy link
Contributor Author

bodgit commented Jan 31, 2024

Closing this PR as it looks like this commit has been cherry-picked into master by 1cf1811.

@bodgit bodgit closed this Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

x/crypto: AcceptSecContext always given first outputToken from InitSecContext
2 participants