Solution
For list of reasons WinSCP cannot parse directory listing and possible resolutions, see documentation.
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
10.3 does not have SFTP.
WinSCP cannot read date in this format. I suppose that there must be a way how to force 10.3 to use standard format.
Unfortunately, this is a bug in 10.3. I filed a radar, #3473836, which looks like it will be fixed in some upcoming 10.3.x release.
WinSCP cannot read date in this format. I suppose that there must be a way how to force 10.3 to use standard format.
Are there any options or workarounds in WinSCP that will instruct it to ignore the reversed date listing in 10.3 ? Alternatively, is there a way to instruct "ls" on 10.3 to use the old date format? 10.3 does not have SFTP.
It appears there is a new column in the ls command for 10.3:
10.2:
drwxr-xr-x 26 jochs staff 884 Oct 25 21:37 .
drwxrwxr-t 6 root wheel 204 Jun 15 23:26 ..
10.3:
drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .
drwxrwxr-t 5 root admin 170 5 Oct 21:54 ..
This particular problem with tcsh may be solved. But in general WinsCP will not work with tcsh, because the shell behaves incorrectly with non-interactive shell (WinSCP case).
You may specify /bin/bash shell on SCP tab of login dialog. So you may keep tcsh as default user shell.
And of course, you may use SFTP instead of SCP. SFTP is not influenced by user shell. Next version (very soon), will have much better performance with SFTP that current version.
While SFTP does work, I have also found SCP failing with the same response "Unexpected directory listing line "drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .". Operation aborted". However, this persists even when my shell is manually set to /bin/bash. This is connecting to Mac OS X 10.3 (Panther). Connecting to OS X 10.2 always worked with SCP, even with tcsh.
I have noticed some other oddities in 10.3's SSH - it doesn't seem to support resolving "localhost" to "127.0.0.1" in putty like 10.2 used to, even though my hosts file specifies it properly.
This particular problem with tcsh may be solved. But in general WinsCP will not work with tcsh, because the shell behaves incorrectly with non-interactive shell (WinSCP case).
You may specify /bin/bash shell on SCP tab of login dialog. So you may keep tcsh as default user shell.
And of course, you may use SFTP instead of SCP. SFTP is not influenced by user shell. Next version (very soon), will have much better performance with SFTP that current version.
While SFTP does work, I have also found SCP failing with the same response "Unexpected directory listing line "drwxr-xr-x 16 jochs jochs 544 6 Oct 12:33 .". Operation aborted". However, this persists even when my shell is manually set to /bin/bash. This is connecting to Mac OS X 10.3 (Panther). Connecting to OS X 10.2 always worked with SCP, even with tcsh.
I have noticed some other oddities in 10.3's SSH - it doesn't seem to support resolving "localhost" to "127.0.0.1" in putty like 10.2 used to, even though my hosts file specifies it properly.
This particular problem with tcsh may be solved. But in general WinsCP will not work with tcsh, because the shell behaves incorrectly with non-interactive shell (WinSCP case).
You may specify /bin/bash shell on SCP tab of login dialog. So you may keep tcsh as default user shell.
And of course, you may use SFTP instead of SCP. SFTP is not influenced by user shell. Next version (very soon), will have much better performance with SFTP that current version.