8fbae90 created the issue

I apologize if I should have just reopened the relevant ticket I found, but I wasn't sure if that was the right thing to do or not, since I'm not one of the developers.

Anyway... I ran across old ticket #143 (while searching for an unrelated topic before making a post) and I would submit that the "wontfix" resolution may not be the optimal action in that case.

I believe you could avoid the regression bug mentioned by merely making a second attempt to transfer filenames with leading whitespace. -- I.e. Try once with the whitespace in the name, then if it fails, try again without the whitespace.

This "retry" behavior should be applied to any operation such as permission changes, renames, etc. on files believed to have leading whitespace ... not just downloads, of course.