-
Notifications
You must be signed in to change notification settings - Fork 18k
x/crypto/ssh: KeyboardInteractiveChallenge error message is incorrect #41823
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
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
This seems like it should be pretty trivial to change, and I'd be happy to submit a PR. The contribution guide said it was best to submit an issue first so I filed this as well. |
Yes, filing an issue and discussing it first is very helpful, thanks. CC @FiloSottile per owners. |
Change https://golang.org/cl/259902 mentions this issue: |
c-expert-zigbee
added a commit
to c-expert-zigbee/crypto_go
that referenced
this issue
Mar 28, 2022
Fixes golang/go#41823 Change-Id: I4653f23239bdf2ab472d3d15c6653b89ebf7ccd4 GitHub-Last-Rev: 179b3ee0efc7b4733da9fbbd8e5ec73a72ef8156 GitHub-Pull-Request: golang/crypto#158 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/259902 Trust: Roland Shoemaker <roland@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
c-expert-zigbee
added a commit
to c-expert-zigbee/crypto_go
that referenced
this issue
Mar 28, 2022
Fixes golang/go#41823 Change-Id: I4653f23239bdf2ab472d3d15c6653b89ebf7ccd4 GitHub-Last-Rev: 179b3ee0efc7b4733da9fbbd8e5ec73a72ef8156 GitHub-Pull-Request: golang/crypto#158 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/259902 Trust: Roland Shoemaker <roland@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
c-expert-zigbee
added a commit
to c-expert-zigbee/crypto_go
that referenced
this issue
Mar 29, 2022
Fixes golang/go#41823 Change-Id: I4653f23239bdf2ab472d3d15c6653b89ebf7ccd4 GitHub-Last-Rev: 179b3ee0efc7b4733da9fbbd8e5ec73a72ef8156 GitHub-Pull-Request: golang/crypto#158 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/259902 Trust: Roland Shoemaker <roland@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
c-expert-zigbee
added a commit
to c-expert-zigbee/crypto_go
that referenced
this issue
Mar 29, 2022
Fixes golang/go#41823 Change-Id: I4653f23239bdf2ab472d3d15c6653b89ebf7ccd4 GitHub-Last-Rev: 179b3ee0efc7b4733da9fbbd8e5ec73a72ef8156 GitHub-Pull-Request: golang/crypto#158 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/259902 Trust: Roland Shoemaker <roland@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
LewiGoddard
pushed a commit
to LewiGoddard/crypto
that referenced
this issue
Feb 16, 2023
Fixes golang/go#41823 Change-Id: I4653f23239bdf2ab472d3d15c6653b89ebf7ccd4 GitHub-Last-Rev: 179b3ee0efc7b4733da9fbbd8e5ec73a72ef8156 GitHub-Pull-Request: golang/crypto#158 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/259902 Trust: Roland Shoemaker <roland@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
BiiChris
pushed a commit
to BiiChris/crypto
that referenced
this issue
Sep 15, 2023
Fixes golang/go#41823 Change-Id: I4653f23239bdf2ab472d3d15c6653b89ebf7ccd4 GitHub-Last-Rev: 179b3ee GitHub-Pull-Request: golang#158 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/259902 Trust: Roland Shoemaker <roland@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
desdeel2d0m
added a commit
to desdeel2d0m/crypto
that referenced
this issue
Jul 1, 2024
Fixes golang/go#41823 Change-Id: I4653f23239bdf2ab472d3d15c6653b89ebf7ccd4 GitHub-Last-Rev: 179b3ee0efc7b4733da9fbbd8e5ec73a72ef8156 GitHub-Pull-Request: golang/crypto#158 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/259902 Trust: Roland Shoemaker <roland@golang.org> Run-TryBot: Filippo Valsorda <filippo@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I haven't checked, but the error message is the same on the master branch.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
When using the ssh.KeyboardInteractiveChallenge authentication method, I returned
answers []string
that was larger in size than the the inputquestions []string
. I then passed this config to ssh.Dial.What did you expect to see?
ssh.Dial
should fail with an error message saying too many answers were provided for the questions asked by the challenge.What did you see instead?
ssh.Dial
failed with the error messagessh: not enough answers from keyboard-interactive callback
.The text was updated successfully, but these errors were encountered: