That's partly issue of FAR. If current path ends with slash, FAR will not select leaved folder when parent directory is opened. On the other hand if it does not end with slash, there are other issues (but that's for different topic). WinSCP for that reason does not add the slash. But it seems that freeSSHd does it on its own.

Anyway, this issue has been added to tracker.

Aditional info about the freeSSHd sever:



Session protocol = SSH-2
SSH implementation = WeOnlyDo 2.0.3
Encryption algorithm = aes
Compression = No
File transfer protocol = SFTP-3
------------------------------------------------------------
Can change permissions = Yes
Can change owner/group = No
Can execute arbitrary command = No
Can create symlink/hardlink = Yes/No
Can lookup user groups = No
Can duplicate remote files = No
Can check available space = No
Can calculate file checksum = No
Native text (ASCII) mode transfers = No
------------------------------------------------------------
Additional protocol information
The server does not support any SFTP extension.

Hello,

I've been using freeSSHd 1.2.1 (latest) and Far Plugin 1.6.1. There is a slight problem when I change to parent directory (..) the cursor doesn't go to the directory that I've just been in, but instead goes to (..)

For example, let's say I'm in /dir1/dir2/. If I go up-dir and go to /dir1/, the cursor should be positioned on dir2, but instead it goes to the first item (..)

I presume it's some kind of shortcoming of freeSSHd as working with linux servers works as expected. Trouble is freeSSHd is the only decent free Windows SFTP server that I've found.

The question is ... can something be modified in WinSCP's setting's or freeSSHd's settings to mitigate this behavior, or is there some quick tweak you can do to solve this problem?

Thanks