Skip to content

copytool: support native Windows OpenSSH - #5299

Open
jandubois wants to merge 1 commit into
lima-vm:masterfrom
jandubois:copytool-native-windows-openssh
Open

copytool: support native Windows OpenSSH#5299
jandubois wants to merge 1 commit into
lima-vm:masterfrom
jandubois:copytool-native-windows-openssh

Conversation

@jandubois

@jandubois jandubois commented Jul 21, 2026

Copy link
Copy Markdown
Member

On Windows, limactl copy converted host paths to the Cygwin/MSYS form no matter which tool would consume them, and it passed ControlMaster options unconditionally. Native OpenSSH cannot use that path form and has no multiplexing, so scp failed with getsockname failed.

The two backends need different path forms, so every path now takes the form of the binary that reads it. Both also skip multiplexing on Windows.

Part of the native Windows OpenSSH series. It can merge in any order, except that #5337 appends to the same test file, so whichever lands second needs a trivial rebase there. The Windows jobs exercise only the Cygwin scp path, because the runners carry no rsync of their own. That coverage and validation on a plain Windows host both arrive with the CI jobs in #5342.

Assisted-by: Claude Opus 5

On Windows, `limactl copy` converted host paths to the Cygwin/MSYS form
no matter which tool would consume them, and it passed ControlMaster
options unconditionally. Native OpenSSH cannot use that path form and
has no multiplexing, so scp failed with "getsockname failed".

The two backends need different path forms. scp takes whatever its own
toolchain uses, while rsync on Windows is always Cygwin-based and reads
a drive letter as a hostspec. So every path now takes the form of the
binary that reads it, operands and ssh options alike, because scp hands
its options to the ssh beside itself while rsync hands them to the ssh
it names.

Both backends now skip multiplexing on Windows, so they stop building
a control socket path they never use.

Signed-off-by: Jan Dubois <jan.dubois@suse.com>
@jandubois
jandubois force-pushed the copytool-native-windows-openssh branch from a5a9836 to 628fa44 Compare July 27, 2026 06:41
@jandubois

Copy link
Copy Markdown
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants