-
Notifications
You must be signed in to change notification settings - Fork 471
Make it possible to only allow one channel per connection #7
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
Comments
In particular, at the session channel level. This loops through all session channel requests and allows all of them. |
So maybe some kind of session policy callback? |
This is one of the ones I'm not too sure on the design of. When we implemented this we just hard-coded it but I know that's not what most people want. A session policy callback would work. |
progrium
pushed a commit
that referenced
this issue
Feb 23, 2019
* Add SessionPolicyCallback Closes #7 * Update docs related to the embedded sync.Locker in the Context * Fix mutex in context
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running a fairly large SSH service and we've been looking at moving to an ssh wrapper library (rather than working on our own) and this is one of the things we do to make it easier to scale (so we know there's only one operation happening on each host)
The text was updated successfully, but these errors were encountered: