Dolphin uses fish: instead of sftp: for "SSH" connections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Base |
New
|
Undecided
|
Unassigned | ||
dolphin (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned | ||
kdebase-runtime (Ubuntu) |
Fix Released
|
Wishlist
|
Harald Sitter | ||
kdelibs (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: dolphin
When you make a "SSH" Network folder in Dolphin it uses the obsolescent fish protocol instead of sftp. Any Ubuntu server that has ssh installed supports sftp without additional configuration required.
Fish is problematic because it operates by attempting to drop a small perl script on the far end of the connection and will make multiple parallel connections rather than transfer files in sequence. In my case this is incompatible with server rate limits in the server firewall rendering the ability to make network folders useless.
While there is possbily some utility in offering fish as an alternative in the unlikely event sftp is not supported, it should not be the primary/only protocol for network connections over ssh.
Related branches
Changed in kdebase: | |
assignee: | nobody → apachelogger |
status: | Confirmed → In Progress |
Confirmed fish instead of sftp in Dolphin. Set to High due to the possible? security risk.