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
x/crypto/ssh: add ServerConfig.NoClientAuthCallback #51994
Comments
Change https://go.dev/cl/395314 mentions this issue: |
It was possible to accept auth type "none" before, but not dynamically at runtime as a function of the ConnMetadata like the other auth types' callback hooks. See golang/go#51994 and https://go-review.googlesource.com/c/crypto/+/395314 Change-Id: I83ea80901d4977d8f78523e3d1e16e0a7df5b172 (cherry picked from commit 4a431fab27b09acb1458fbb8709e12b2760e58a2)
/cc @FiloSottile |
This proposal has been added to the active column of the proposals project |
/cc @golang/security |
Does anyone object to adding this? It is a very small CL and Roland has already +2'ed it. |
Based on the discussion above, this proposal seems like a likely accept. |
No change in consensus, so accepted. |
It was possible to accept auth type "none" before, but not dynamically at runtime as a function of the ConnMetadata like the other auth types' callback hooks. See golang/go#51994 and https://go-review.googlesource.com/c/crypto/+/395314 this commit is pick from golang@6211952
It was possible to accept auth type "none" before, but not dynamically at runtime as a function of the ConnMetadata like the other auth types' callback hooks. See golang/go#51994 and https://go-review.googlesource.com/c/crypto/+/395314 Change-Id: I83ea80901d4977d8f78523e3d1e16e0a7df5b172 (cherry picked from commit 4a431fab27b09acb1458fbb8709e12b2760e58a2)
It was possible to accept auth type "none" before, but not dynamically at runtime as a function of the ConnMetadata like the other auth types' callback hooks. See golang/go#51994 and https://go-review.googlesource.com/c/crypto/+/395314 Change-Id: I83ea80901d4977d8f78523e3d1e16e0a7df5b172 (cherry picked from commit 4a431fab27b09acb1458fbb8709e12b2760e58a2)
It was possible to accept auth type "none" before, but not dynamically at runtime as a function of the ConnMetadata like the other auth types' callback hooks. See golang/go#51994 and https://go-review.googlesource.com/c/crypto/+/395314 Change-Id: I83ea80901d4977d8f78523e3d1e16e0a7df5b172 (cherry picked from commit 4a431fab27b09acb1458fbb8709e12b2760e58a2)
Currently Go's SSH package doesn't permit a server to conditionally permit auth type "none" at runtime. There's a
NoClientAuth bool
flag to globally enable it, but you can't decide as a function of theConnMetaData
(username, IPs, etc) whether to permit it.I propose adding a
ServerConfig.NoClientAuthCallback
auth hook, with a signature like the existing auth hooks:I sent https://go-review.googlesource.com/c/crypto/+/395314 which @rolandshoemaker approved, but this is the proposal for the API change.
/cc @maisem
The text was updated successfully, but these errors were encountered: