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: disable wantReply in some requests to comply with OpenSSH #96

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ilyaluk-old
Copy link

@ilyaluk-old ilyaluk-old commented Aug 19, 2019

@gopherbot
Copy link
Contributor

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

Please visit https://go-review.googlesource.com/c/crypto/+/190777 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

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 2: Commit message was updated.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 3: Commit message was updated.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

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

Please visit https://go-review.googlesource.com/c/crypto/+/190777 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

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 6: Commit message was updated.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@ilyaluk-old ilyaluk-old changed the title x/crypto: disable wantReply in auth-agent-req to comply with OpenSSH ssh: disable wantReply in auth-agent-req to comply with OpenSSH Sep 3, 2019
@ilyaluk-old ilyaluk-old changed the title ssh: disable wantReply in auth-agent-req to comply with OpenSSH ssh: disable wantReply in some requests to comply with OpenSSH Sep 3, 2019
@gopherbot
Copy link
Contributor

Message from Brad Fitzpatrick:

Patch Set 9:

No changes to tests?


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 9:

Patch Set 9:

No changes to tests?

Apparently, it's not tested in code, because sshd is used to test client, as far as I understand. OpenSSH server seems to be okay with any implementation (it checks wantReply in any case).


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Brad Fitzpatrick:

Patch Set 9:

Let me put it another way: what's broken?

Add a test that's broken but is fixed with this change.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Go Bot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 2: Commit message was updated.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 3: Commit message was updated.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 6: Commit message was updated.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Brad Fitzpatrick:

Patch Set 9:

No changes to tests?


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Ilya Lukyanov:

Patch Set 9:

Patch Set 9:

No changes to tests?

Apparently, it's not tested in code, because sshd is used to test client, as far as I understand. OpenSSH server seems to be okay with any implementation (it checks wantReply in any case).


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Brad Fitzpatrick:

Patch Set 9:

Let me put it another way: what's broken?

Add a test that's broken but is fixed with this change.


Please don’t reply on this GitHub thread. Visit golang.org/cl/190777.
After addressing review feedback, remember to publish your drafts!

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.

4 participants