Skip to content

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

Closed
belak opened this issue Feb 3, 2017 · 3 comments
Closed

Make it possible to only allow one channel per connection #7

belak opened this issue Feb 3, 2017 · 3 comments

Comments

@belak
Copy link
Collaborator

belak commented Feb 3, 2017

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)

@belak
Copy link
Collaborator Author

belak commented Feb 3, 2017

In particular, at the session channel level. This loops through all session channel requests and allows all of them.

@progrium
Copy link
Contributor

progrium commented Feb 3, 2017

So maybe some kind of session policy callback?

@belak
Copy link
Collaborator Author

belak commented Feb 3, 2017

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.

belak added a commit that referenced this issue May 13, 2018
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
Projects
None yet
Development

No branches or pull requests

2 participants