Description
After the asyncssh migration (#44), clicking into the .ssh directory on an SFTP server does nothing — no error shown, no navigation. WinSCP accesses the same directory fine with the same credentials/permissions.
Expected Behavior
Should navigate into the directory and list its contents.
Likely Cause
asyncssh may be sending different SFTP readdir/stat commands, or silently swallowing an error response from the server for hidden/dot-prefixed directories. The failure is not surfaced to the UI at all.
Bitvise is known for strict SFTP spec compliance — asyncssh may be sending a subtly non-standard request that Bitvise rejects, while paramiko and WinSCP are compatible.
Environment
- SFTP Server: Bitvise SSH Server
- Other directories work fine
- Server permissions confirmed correct
- WinSCP works without issues on same server/credentials
Description
After the asyncssh migration (#44), clicking into the
.sshdirectory on an SFTP server does nothing — no error shown, no navigation. WinSCP accesses the same directory fine with the same credentials/permissions.Expected Behavior
Should navigate into the directory and list its contents.
Likely Cause
asyncssh may be sending different SFTP readdir/stat commands, or silently swallowing an error response from the server for hidden/dot-prefixed directories. The failure is not surfaced to the UI at all.
Bitvise is known for strict SFTP spec compliance — asyncssh may be sending a subtly non-standard request that Bitvise rejects, while paramiko and WinSCP are compatible.
Environment