Add support for SSH_OPTIONS_PROXYJUMP - #10
Merged
Merged
Conversation
To make life easier in the future I have added a low-level binding to
ssh_options_set and a high-level wrapper class for Session in Ruby.
I haved merged the C initialize method into the allocator and defined a
new Ruby initialize method. Though evil, `Session.allocate.connect`
should not make the whole Ruby process crash like it does now.
Without authentication the test is not convincing yet, but I could
confirm that `session.add_proxy_jump "localhost"` establishes a
connection to my host’s SSH server using my user’s default keys.
Calling ssh_options_set every time a new proxy jump is added is a bit
wasteful but multiple jumps are rare and the intended API is:
session.add_proxy_jump "foo", authenticate: -> (jump_session) { … }
session.add_proxy_jump "bar", authenticate: -> (jump_session) { … }
Rather than the counter-intuitive libssh way:
session.proxy_jumps = ["foo", "bar"]
session.append_proxy_jump_callback authenticate: -> (jump_session) { … }
session.append_proxy_jump_callback authenticate: -> (jump_session) { … }
-Wno-unused-parameter silences warnings in Ruby’s headers, which used to
cause noise when building.
fwininger
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To make life easier in the future I have added a low-level binding to
ssh_options_set and a high-level wrapper class for Session in Ruby.
I haved merged the C initialize method into the allocator and defined a
new Ruby initialize method. Though evil,
Session.allocate.connectshould not make the whole Ruby process crash like it does now.
Without authentication the test is not convincing yet, but I could
confirm that
session.add_proxy_jump "localhost"establishes aconnection to my host’s SSH server using my user’s default keys.
Calling ssh_options_set every time a new proxy jump is added is a bit
wasteful but multiple jumps are rare and the intended API is:
Rather than the counter-intuitive libssh way:
-Wno-unused-parameter silences warnings in Ruby’s headers, which used to
cause noise when building.