scp error: protocol error: filename does not match request

[FlexMcMurphy]

Hello,

PyScripter-3.6.3-x64-Setup.exe on Windows 7
OpenSSH-Win32.zip Version: v8.1.0.0p1-Beta installed on Win 7 and added to the PATH.
Trying to remote edit/debug script on OSMC running on a Raspberry Pi on the same LAN.

My keys are set up and I can connect to OSMC Pi from Windows 7 command line with: ssh root@osmc

However when I set up the SSH server details in PyScripter like this:

And try to open a file on the OSMC Pi filesystem like this:

Instead I get this error:

If I add the scp option -T into the ssh server settings like this:

Then it does connect.

I can also simply drag and drop the file from a Windows Samba share into the PyScripter IDE and it opens it remotely without any error...

Why do I need to add the -T? According to the scp man page this option disables strict filename checking when copying files from a remote host to a local directory. But why would scp think there has been any change to the remote and local filename in this case? All characters in the remote filename and path are ascii and there are no spaces.

Are there any other scp or ssh options that I should be adding into the PyScripter ssh server settings dialog?

Cheers,

Flex

[pyscripter]

Please https://unix.stackexchange.com/questions/499958/why-does-scps-strict-filename-checking-reject-quoted-last-component-but-not-oth

Basically is a recently introduced bug and adding -T is the workaround.

The default scp/ssh options with OpenSSH are
-o PasswordAuthentication=no -o StrictHostKeyChecking=no

I would be tempted to add -T but I am not sure older OpenSSH version support it.

Please note that when you open a file from a Samba share it will load fine and if you change it it will also save fine. But note that the difference it the displayed name (forward vrs back slashes). When you run such file from PyScripter it typically will run locally. Only by coincidence or carefull naming it will run remotely. I would suggest that python files that you want to run remotely you open them with Open Remote.

[FlexMcMurphy]

Thanks for explaining the difference between File > Open Remote File and dragging a file from Samba share in to the PyScripter IDE.

About the scp error. Yes I already read that link and understand that using -T (or using sftp instead of scp) is a workaround.

But I'm curious why, in my case above, is PyScripter causing scp to give that error? There is nothing unusual about the remote filename:
/home/osmc/python/h7spatterns

Perhaps, as with ansible mentioned here, when scp is used to fetch a file PyScripter will use single quotes around the path causing a validation failure? Is that so do you know?

Flex

[pyscripter]

Perhaps, as with ansible mentioned here, when scp is used to fetch a file PyScripter will use single quotes around the path causing a validation failure? Is that so do you know?

Yes this is the case.

[FlexMcMurphy]

Brilliant. Thank you.