-
Notifications
You must be signed in to change notification settings - Fork 936
Fix SSH relay failure when config has LocalForward/DynamicForward directives #2635
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
Open
bIackr0se
wants to merge
3
commits into
manaflow-ai:main
Choose a base branch
from
bIackr0se:fix/relay-ssh-forward-conflict
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+213
−3
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
c62c6d9
Fix SSH relay failure when config has LocalForward/DynamicForward dir…
bIackr0se 886b0ca
Address review feedback: port regression, StrictHostKeyChecking, IPv6
bIackr0se 2d0298b
Fix critical: revert controlpath from shared filter, harden StrictHos…
bIackr0se File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: manaflow-ai/cmux
Length of output: 355
🏁 Script executed:
Repository: manaflow-ai/cmux
Length of output: 201
🏁 Script executed:
sed -n '4100,4200p' Sources/Workspace.swiftRepository: manaflow-ai/cmux
Length of output: 5003
🏁 Script executed:
Repository: manaflow-ai/cmux
Length of output: 42
🏁 Script executed:
sed -n '4171,4220p' Sources/Workspace.swiftRepository: manaflow-ai/cmux
Length of output: 2262
🏁 Script executed:
sed -n '4176,4180p' Sources/Workspace.swiftRepository: manaflow-ai/cmux
Length of output: 392
🏁 Script executed:
rg "proxyjump|resolveProxyJumpChain" -n Sources/Workspace.swiftRepository: manaflow-ai/cmux
Length of output: 262
The fast-path skips resolving ProxyJump hops that contain SSH config aliases.
The pattern check at lines 4176–4180 returns
hopunchanged if it matchesuser@host:port, assuming it's already fully resolved. However, the host portion can still be an SSH config alias (e.g.,bob@jumpalias:2222wherejumpaliasis a Host alias). This bypasses the resolution logic below and passes the unresolved alias to-J, causing the spawned jump SSH to fail since it inherits-F /dev/null.The shell test demonstrates this:
ssh -G targetreportsproxyjump bob@jumpalias:2222, butjumpaliasresolves tobastion.example.comwhen checked separately. Parse and resolve the host portion of the hop, or only skip literal IP addresses (e.g.,user@192.0.2.1:2222oruser@[::1]:2222).🤖 Prompt for AI Agents