You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so scp with windows for server and client works, but there are some specific interesting things that may need changes to be 'seamless'.
i get protocol error: expected control record on download, this sounds like it is server side somewhere
for my simple test cases so far, the download still succeeds.
upload didn't show this error and it uploaded fine. i had a slight delay in seeing the upload appear in the mounted folder but that might have been a graphical ui bug on my machine
Use the legacy SCP protocol for file transfers instead of
the SFTP protocol. Forcing the use of the SCP protocol
may be necessary for servers that do not implement SFTP,
for backwards-compatibility for particular filename
wildcard patterns and for expanding paths with a ‘~’
prefix for older SFTP servers.
is the scp middleware for all scp clients, or for scp protocol? should i be asking about an sftp middleware instead? or should this scp middleware be able to handle that?
system info
scoop which scp
C:\WINDOWS\System32\OpenSSH\scp.exe
scoop which ssh
C:\WINDOWS\System32\OpenSSH\ssh.exe
ssh -V
OpenSSH_for_Windows_9.2p1, LibreSSL 3.6.2
((Get-Item (Get-Command sshd).Source).VersionInfo.FileVersion)
9.2.3.1
((Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows nt\CurrentVersion\" -Name ProductName).ProductName)
Windows 10 Pro
The text was updated successfully, but these errors were encountered:
so scp with windows for server and client works, but there are some specific interesting things that may need changes to be 'seamless'.
protocol error: expected control record
on download, this sounds like it is server side somewhere-O
on the client (subsystem request failed on channel 0,scp: connection closed PowerShell/Win32-OpenSSH#1945 (comment)) which is (https://man7.org/linux/man-pages/man1/scp.1.html)system info
The text was updated successfully, but these errors were encountered: