Basename cannot contain .. prevents valid filenames from being sent, no sender-side warning

[zulc22]

securing channel...basename cannot contain '..': 'Dragon Quest III - Soshite Densetsu e... (Japan).zip'

This error message prevented a transfer from occurring that took like five minutes to hash all the files, I understand it's probably a security thing to prevent files from going into unintended directories, but shouldn't the search string be '../', or '..\'? The sender side also had no warning for this and just spat EOF after the receiver connected. I think that both of these concerns could be addressed by checking the filenames with the same check on the server side, and that the substring should be changed.

[schollz]

Feel free to make a pr!

[github-actions]

Stale issue message

[Ozoniuss]

What's the expected behaviour if one wants to transfer a file containing \ from Linux to Windows? Say, a\b.txt. At the moment, on Windows it creates (or uses) the a folder, and creates a file named b.txt inside

[zulc22]

i would expect folder&filenames that are invalid on the target OS to drop an error before a transfer is accepted. different thing from what i was experiencing though