Alternative SFTP directory listing parsing

[Brian Huisman]

When you name files on the remote server such that their names begin with a space character, FileZilla is no longer able to operate on those files. It always returns the error "no such file or directory" when trying to move, delete or rename the file.

Another similar bug (#5292) was rejected because it related to a limitation of using the LIST command and the identification of padding characters.

However, I am connecting to my remote server using SSH and FileZilla is using the "ls" command, rather than LIST. Another difference is that, when using LIST, if the file either begins or ends with a space, it becomes unmodifiable, while with ls, files ending with a space can be interacted with normally. Only files that begin with a space become problematic.

Using FZ 3.3.2.1

[Tim Kosse]

Note that SFTP is an entirely different protocol.

Theoretically SFTP does provided the ability to detect leading spaces, however a great many servers violate the SFTP specifications and do not properly provided the server-prepared, pre-parsed data. As such the pre-parsed data has not yet been used by FileZilla.