Actions
Bug #26897
closed
ssh/session needs explicit support for Puma
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Description
The ssh/session API hijakcs the request socket and upgrades it to a different protocol that runs a interactive ssh session.
With webrick, the request socket is either a normal IO socket, or a OpenSSL::SSLSocket, depending on whether the connection uses TLS or not. A OpenSSL::SSLSocket can not be directly used with the Net:SSH event loop, so there is some glue to make it stick.
With Puma, we get a Puma::MiniSSL::Socket, which requires its own glue.
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/43 added
Updated by Anonymous over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_proxy_plugin|0a1f59ff8258154542e1bedc4a7c7c579087a557.
Updated by Adam Ruzicka almost 5 years ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.3.0 added
Actions